Snap Areas > Edges & Corners are no longer supported on external monitor

[ErHaWeb]

• [x] This is a new bug that hasn't been documented in a closed issue or in the Readme.

macOS version: Version 13.5.2 (Build 22G91) Rectangle version: Rectangle Pro v3.0.9 (150) Model: MacBookPro18,3 [3]

For a few days now, the Snap Areas > Edges & Corners function on my external monitor no longer works when my MacBook is closed and I use the external monitor exclusively.

If I leave the MacBook open I could observe that it makes a difference on which monitor the window was placed before.

If the window was previously placed on the MacBook screen, while dragging the window with the mouse, the snap areas are displayed on both monitors and snapping works.

If the window was previously placed on my external monitor, neither the external monitor nor the MacBook monitor will show the snap areas and snapping will not work while dragging the window with the mouse.

Here is a video recording of the described behavior. During the recording the following log was created:

2023-09-20T10:32:02+02:00: AX sizing proposed: (756.0, 944.0), result: (756.0, 529.0)
2023-09-20T10:32:02+02:00: AX position proposed: (5120.0, 496.0), result: (5120.0, 496.0)
2023-09-20T10:32:02+02:00: AX sizing proposed: (756.0, 944.0), result: (756.0, 944.0)
2023-09-20T10:32:02+02:00: leftHalf | display: (5120.0, 0.0, 1512.0, 944.0), calculatedRect: (5120.0, 496.0, 756.0, 944.0), resultRect: (5120.0, 496.0, 756.0, 944.0), srcScreen: Built-in Retina Display, destScreen: Built-in Retina Display, resultScreen: Built-in Retina Display
2023-09-20T10:32:04+02:00: AX position proposed: (5289.08984375, 496.0), result: (5289.0, 496.0)
2023-09-20T10:32:04+02:00: AX sizing proposed: (555.0, 436.0), result: (555.0, 436.0)
2023-09-20T10:32:10+02:00: AX sizing proposed: (2560.0, 1415.0), result: (2560.0, 908.0)
2023-09-20T10:32:10+02:00: AX position proposed: (2560.0, 25.0), result: (2560.0, 25.0)
2023-09-20T10:32:10+02:00: AX sizing proposed: (2560.0, 1415.0), result: (2560.0, 1415.0)
2023-09-20T10:32:10+02:00: rightHalf | display: (0.0, 0.0, 5120.0, 1415.0), calculatedRect: (2560.0, 25.0, 2560.0, 1415.0), resultRect: (2560.0, 25.0, 2560.0, 1415.0), srcScreen: LG HDR DQHD, destScreen: LG HDR DQHD, resultScreen: LG HDR DQHD
2023-09-20T10:32:24+02:00: AX sizing proposed: (504.0, 944.0), result: (504.0, 944.0)
2023-09-20T10:32:24+02:00: AX position proposed: (5120.0, 496.0), result: (5120.0, 496.0)
2023-09-20T10:32:24+02:00: AX sizing proposed: (504.0, 944.0), result: (504.0, 944.0)
2023-09-20T10:32:24+02:00: firstThird | display: (5120.0, 0.0, 1512.0, 944.0), calculatedRect: (5120.0, 496.0, 504.0, 944.0), resultRect: (5120.0, 496.0, 504.0, 944.0), srcScreen: Built-in Retina Display, destScreen: Built-in Retina Display, resultScreen: Built-in Retina Display
2023-09-20T10:32:25+02:00: AX position proposed: (4934.6015625, 496.0), result: (4934.0, 496.0)
2023-09-20T10:32:25+02:00: AX sizing proposed: (756.0, 944.0), result: (756.0, 944.0)
2023-09-20T10:32:28+02:00: AX sizing proposed: (1706.0, 1415.0), result: (833.0, 1415.0)
2023-09-20T10:32:28+02:00: AX position proposed: (3414.0, 25.0), result: (3414.0, 25.0)
2023-09-20T10:32:28+02:00: AX sizing proposed: (1706.0, 1415.0), result: (1706.0, 1415.0)
2023-09-20T10:32:28+02:00: lastThird | display: (0.0, 0.0, 5120.0, 1415.0), calculatedRect: (3414.0, 25.0, 1706.0, 1415.0), resultRect: (3414.0, 25.0, 1706.0, 1415.0), srcScreen: LG HDR DQHD, destScreen: LG HDR DQHD, resultScreen: LG HDR DQHD

Thank you in advance for investigating the problem. I would be very happy if I could use this beloved function on my external monitor again in the future.

[rxhanson]

Thanks for reporting. Here's a similar issue: https://github.com/rxhanson/RectanglePro-Community/issues/353.

I'll be adding in a way to revert back to the previous way that window snapping works, but there's a tradeoff here - the reason for the change was because of a macOS bug that messed up table views created by SwiftUI.

[ErHaWeb]

Thanks for the information and sorry for the duplicate. I must have been blind this morning not to have found this problem.