Window repositioning and layout management isn't working as expected

[andupotorac]

1. The size of the screen where the movements happens seems to be relative to the laptop, even if I have larger screens connected to it and want to position windows with CTRL+CMD. It also jumps to other screens instead of staying on the same screen.

2. The feature I really needed was to position the windows to the same spot when the mac is opened again. There are layouts, for some reason requiring each to be set individually, instead of saving all desktops and window positions and sizes as they are. And when you come back, they're not placed in the spot they were before, even if you try to manually replace them one at a time.

I hoped this is the app that handles window positions, but it turns out it isn't. :(

[rxhanson]

Sorry for the delay.

The size of the screen where the movements happens seems to be relative to the laptop, even if I have larger screens connected to it and want to position windows with CTRL+CMD. It also jumps to other screens instead of staying on the same screen.

I'm not quite sure I understand. One place that you can adjust the next/prev display functionality is in the "Repeated commands" section of the gear tab in the Settings window. Perhaps a little more detail about the command you're performing and the result would help me understand?

The feature I really needed was to position the windows to the same spot when the mac is opened again. There are layouts, for some reason requiring each to be set individually, instead of saving all desktops and window positions and sizes as they are. And when you come back, they're not placed in the spot they were before, even if you try to manually replace them one at a time.

By "desktops", if you're referring to Spaces, then there is no publicly available API for moving windows across Spaces. If you're referring to displays, then this is a bit of a limitation of the app that I have plans to adjust, although you can save a layout of each display separately and drag & drop each of the individual app layouts into one layout. There are some timing issues inherent to macOS and certain external displays that make it difficult to properly apply layouts upon wake, and there's simply not an excellent workaround for this that I'm aware of.

[hendomuller]

Hello! I am having much the same problem. I am using Rectangle Pro on a MacBook Pro and an Apple Studio Display. Everything was working fine for months and then all of a sudden Rectangle Pro is acting weird. While using the MacBook Pro in clamshell mode (laptop closed and connected via Thunderbolt 4 to the Studio Display), the keyboard commands which I most often use (Almost Maximize, Left Half, and Right Half) seems to now think that the Studio Display has the horizontal width of the MacBook Pro. If I unplug the computer from the external display and just use it, the relative dimensions are no longer being used.

The strange thing is that this started happening a few weeks ago without any change to my configuration or system software — after working perfectly for several months.

Anyone have any idea what I might do? Thank you for reading.

Michael

[rxhanson]

Would you mind adding some logging that shows what's going on when this happens? Hold the option key in the menu bar menu and select View Logging, then reproduce the issue.

[hendomuller]

Thank you for the quick reply. I updated to Sequoia 15.1.1 a few minutes ago and it seems to work a little better. But here is a log file that shows a bit of what I was referring to: 2024-11-21T11:53:38-05:00: Updating visible window info 2024-11-21T11:53:46-05:00: Current frame is equal to new frame 2024-11-21T11:53:49-05:00: Current frame is equal to new frame 2024-11-21T11:53:51-05:00: Updating visible window info 2024-11-21T11:53:52-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1415.0) 2024-11-21T11:53:52-05:00: AX position proposed: (0.0, 25.0), result: (-0.0, 25.0) 2024-11-21T11:53:52-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1415.0) 2024-11-21T11:53:52-05:00: leftHalf | display: (0.0, 0.0, 2160.0, 1415.0), calculatedRect: (0.0, 25.0, 1080.0, 1415.0), resultRect: (-0.0, 25.0, 1080.0, 1415.0), srcScreen: Studio Display, destScreen: Studio Display, resultScreen: Studio Display 2024-11-21T11:53:54-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1415.0) 2024-11-21T11:53:54-05:00: AX position proposed: (1080.0, 25.0), result: (1080.0, 25.0) 2024-11-21T11:53:54-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1415.0) 2024-11-21T11:53:54-05:00: rightHalf | display: (0.0, 0.0, 2160.0, 1415.0), calculatedRect: (1080.0, 25.0, 1080.0, 1415.0), resultRect: (1080.0, 25.0, 1080.0, 1415.0), srcScreen: Studio Display, destScreen: Studio Display, resultScreen: Studio Display 2024-11-21T11:53:55-05:00: AX sizing proposed: (2160.0, 1415.0), result: (1480.0, 1415.0) 2024-11-21T11:53:55-05:00: AX position proposed: (0.0, 25.0), result: (0.0, 25.0) 2024-11-21T11:53:55-05:00: AX sizing proposed: (2160.0, 1415.0), result: (2160.0, 1415.0) 2024-11-21T11:53:55-05:00: maximize | display: (0.0, 0.0, 2160.0, 1415.0), calculatedRect: (0.0, 25.0, 2160.0, 1415.0), resultRect: (-0.0, 25.0, 2160.0, 1415.0), srcScreen: Studio Display, destScreen: Studio Display, resultScreen: Studio Display 2024-11-21T11:54:03-05:00: Updating visible window info 2024-11-21T11:54:07-05:00: Updating visible window info

…

On Nov 21, 2024, at 11:43 AM, Ryan Hanson ***@***.***> wrote: Would you mind adding some logging that shows what's going on when this happens? Hold the option key in the menu bar menu and select View Logging, then reproduce the issue. — Reply to this email directly, view it on GitHub <#583 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BND5PNTBENGI5ILVNBAYOND2BYESJAVCNFSM6AAAAABSHJATE2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZTHEYDENI>. You are receiving this because you commented.

[hendomuller]

Here is another log: 2024-11-21T12:27:21-05:00: Updating visible window info 2024-11-21T12:27:31-05:00: AX sizing proposed: (809.0, 1364.0), result: (809.0, 1364.0) 2024-11-21T12:27:31-05:00: AX position proposed: (676.0, 50.0), result: (676.0, 50.0) 2024-11-21T12:27:31-05:00: AX sizing proposed: (809.0, 1364.0), result: (809.0, 1364.0) 2024-11-21T12:27:31-05:00: center | display: (0.0, 0.0, 2160.0, 1415.0), calculatedRect: (676.0, 50.0, 809.0, 1364.0), resultRect: (676.0, 50.0, 809.0, 1364.0), srcScreen: Studio Display, destScreen: Studio Display, resultScreen: Studio Display 2024-11-21T12:27:35-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1390.0) 2024-11-21T12:27:35-05:00: AX position proposed: (1080.0, 25.0), result: (1080.0, 25.0) 2024-11-21T12:27:35-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1415.0) 2024-11-21T12:27:35-05:00: rightHalf | display: (0.0, 0.0, 2160.0, 1415.0), calculatedRect: (1080.0, 25.0, 1080.0, 1415.0), resultRect: (1080.0, 25.0, 1080.0, 1415.0), srcScreen: Studio Display, destScreen: Studio Display, resultScreen: Studio Display 2024-11-21T12:27:37-05:00: Current frame is equal to new frame 2024-11-21T12:27:38-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1415.0) 2024-11-21T12:27:38-05:00: AX position proposed: (0.0, 25.0), result: (0.0, 25.0) 2024-11-21T12:27:38-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1415.0) 2024-11-21T12:27:38-05:00: leftHalf | display: (0.0, 0.0, 2160.0, 1415.0), calculatedRect: (0.0, 25.0, 1080.0, 1415.0), resultRect: (0.0, 25.0, 1080.0, 1415.0), srcScreen: Studio Display, destScreen: Studio Display, resultScreen: Studio Display 2024-11-21T12:27:48-05:00: Updating visible window info 2024-11-21T12:27:55-05:00: Updating visible window info

…

On Nov 21, 2024, at 11:55 AM, Michael Muller ***@***.***> wrote: Thank you for the quick reply. I updated to Sequoia 15.1.1 a few minutes ago and it seems to work a little better. But here is a log file that shows a bit of what I was referring to: 2024-11-21T11:53:38-05:00: Updating visible window info 2024-11-21T11:53:46-05:00: Current frame is equal to new frame 2024-11-21T11:53:49-05:00: Current frame is equal to new frame 2024-11-21T11:53:51-05:00: Updating visible window info 2024-11-21T11:53:52-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1415.0) 2024-11-21T11:53:52-05:00: AX position proposed: (0.0, 25.0), result: (-0.0, 25.0) 2024-11-21T11:53:52-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1415.0) 2024-11-21T11:53:52-05:00: leftHalf | display: (0.0, 0.0, 2160.0, 1415.0), calculatedRect: (0.0, 25.0, 1080.0, 1415.0), resultRect: (-0.0, 25.0, 1080.0, 1415.0), srcScreen: Studio Display, destScreen: Studio Display, resultScreen: Studio Display 2024-11-21T11:53:54-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1415.0) 2024-11-21T11:53:54-05:00: AX position proposed: (1080.0, 25.0), result: (1080.0, 25.0) 2024-11-21T11:53:54-05:00: AX sizing proposed: (1080.0, 1415.0), result: (1080.0, 1415.0) 2024-11-21T11:53:54-05:00: rightHalf | display: (0.0, 0.0, 2160.0, 1415.0), calculatedRect: (1080.0, 25.0, 1080.0, 1415.0), resultRect: (1080.0, 25.0, 1080.0, 1415.0), srcScreen: Studio Display, destScreen: Studio Display, resultScreen: Studio Display 2024-11-21T11:53:55-05:00: AX sizing proposed: (2160.0, 1415.0), result: (1480.0, 1415.0) 2024-11-21T11:53:55-05:00: AX position proposed: (0.0, 25.0), result: (0.0, 25.0) 2024-11-21T11:53:55-05:00: AX sizing proposed: (2160.0, 1415.0), result: (2160.0, 1415.0) 2024-11-21T11:53:55-05:00: maximize | display: (0.0, 0.0, 2160.0, 1415.0), calculatedRect: (0.0, 25.0, 2160.0, 1415.0), resultRect: (-0.0, 25.0, 2160.0, 1415.0), srcScreen: Studio Display, destScreen: Studio Display, resultScreen: Studio Display 2024-11-21T11:54:03-05:00: Updating visible window info 2024-11-21T11:54:07-05:00: Updating visible window info > On Nov 21, 2024, at 11:43 AM, Ryan Hanson ***@***.***> wrote: > > > Would you mind adding some logging that shows what's going on when this happens? Hold the option key in the menu bar menu and select View Logging, then reproduce the issue. > > — > Reply to this email directly, view it on GitHub <#583 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BND5PNTBENGI5ILVNBAYOND2BYESJAVCNFSM6AAAAABSHJATE2VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZTHEYDENI>. > You are receiving this because you commented. >