Snap Area doesn't work since update to Version 3.0.9 (150)

[FL0R1AN84]

Since I installed the update to version 3.0.9 (150) today, the Snap Area is no longer displayed to me. As a test, I deactivated and reactivated this and changed the location of Snap Panel.

My Settings:

My System:

MacBook Pro
Apple M2
macOS 13.5.2

[rxhanson]

Thanks for letting me know. Would you mind seeing if we get any logs for when this happens? Hold the option key in the menu bar menu and select View Logging.

Also, if you click and drag more slowly does it work?

[rxhanson]

One more thing that might help is if you attach your config so I can load it in and replicate your setup. You can export it from the settings tab of the preferences window. Thanks!

[FL0R1AN84]

That's all I got from the log. When I move the window, nothing changes in the log:

2023-09-18T20:03:15+02:00: Rectangle Pro v3.0.9 (150)
macOS: Version 13.5.2 (Build 22G91)
Model: Macmini9,1 [3]
License activation: xxx@xxx.xx (2022-03-24 20:50:19 +0000)

I'm currently using it on my Mac mini and it doesn't work here either

[FL0R1AN84]

My configuration:
RectangleProConfig.json.zip

[rxhanson]

Thanks! Can you try v3.0.10 (beta) and let me know if it fixes the issue?

https://rectangleapp.com/pro/downloads/Rectangle%20Pro%203.0.10.dmg

[BrMBr]

Hi, I'm facing the same issue even after completely uninstalling and reinstalling the app. Thanks

[FL0R1AN84]

Unfortunately not, log also remains empty

2023-09-19T12:39:38+02:00: Rectangle Pro v3.0.10 (151)
macOS: Version 13.5.2 (Build 22G91)
Model: Mac14,7 [3]
License activation: xxx@xxx.xx (2023-01-02 08:12:06 +0000)

[BrMBr]

Update: I carried out some tests here, and the issue on my end appears to be related to the Quick Shade app. When Quick Shade is open, Rectangle (Snap Area) stops working. Once I close Quick Shade, Rectangle functions properly again. Unfortunately, my log is also empty. Hope it helps.

[FL0R1AN84]

@BrMBr Yeah!

I can confirm that when I close the app "Quick Shade" everything works fine again.

2023-09-19T22:03:10+02:00: Rectangle Pro v3.0.9 (150)
macOS: Version 13.5.2 (Build 22G91)
Model: Macmini9,1 [3]
License activation: xxx@xxx.xx (2022-03-24 20:50:19 +0000)
2023-09-19T22:03:16+02:00: AX sizing proposed: (2293.0, 1415.0), result: (2293.0, 1415.0)
2023-09-19T22:03:16+02:00: AX position proposed: (0.0, 25.0), result: (0.0, 25.0)
2023-09-19T22:03:16+02:00: AX sizing proposed: (2293.0, 1415.0), result: (2293.0, 1415.0)
2023-09-19T22:03:16+02:00: firstTwoThirds | display: (0.0, 0.0, 3440.0, 1415.0), calculatedRect: (0.0, 25.0, 2293.0, 1415.0), resultRect: (0.0, 25.0, 2293.0, 1415.0), srcScreen: LG HDR WQHD, destScreen: LG HDR WQHD, resultScreen: LG HDR WQHD
2023-09-19T22:03:17+02:00: AX position proposed: (57.0, 79.0), result: (57.0, 79.0)
2023-09-19T22:03:17+02:00: AX sizing proposed: (2293.0, 1415.0), result: (2293.0, 1415.0)
2023-09-19T22:03:19+02:00: AX sizing proposed: (3440.0, 1415.0), result: (3369.0, 1415.0)
2023-09-19T22:03:19+02:00: AX position proposed: (0.0, 25.0), result: (0.0, 25.0)
2023-09-19T22:03:19+02:00: AX sizing proposed: (3440.0, 1415.0), result: (3440.0, 1415.0)
2023-09-19T22:03:19+02:00: maximize | display: (0.0, 0.0, 3440.0, 1415.0), calculatedRect: (0.0, 25.0, 3440.0, 1415.0), resultRect: (-0.0, 25.0, 3440.0, 1415.0), srcScreen: LG HDR WQHD, destScreen: LG HDR WQHD, resultScreen: LG HDR WQHD
2023-09-19T22:03:22+02:00: AX sizing proposed: (2293.3333333333335, 1415.0), result: (2293.0, 1415.0)
2023-09-19T22:03:22+02:00: AX position proposed: (573.0, 25.0), result: (573.0, 25.0)
2023-09-19T22:03:22+02:00: AX sizing proposed: (2293.3333333333335, 1415.0), result: (2293.0, 1415.0)
2023-09-19T22:03:22+02:00: centerTwoThirds | display: (0.0, 0.0, 3440.0, 1415.0), calculatedRect: (573.0, 25.0, 2293.3333333333335, 1415.0), resultRect: (573.0, 25.0, 2293.0, 1415.0), srcScreen: LG HDR WQHD, destScreen: LG HDR WQHD, resultScreen: LG HDR WQHD

[rxhanson]

Thanks! The bug fix that went into v3.0.9 was a workaround for a macOS bug that caused glitchy behavior in table views in other parts of macOS and other apps. I'll create a release where you can use a terminal command to switch between these two implementations (prior to 3.0.9 and after), and I'll post back when it's ready.

[ErHaWeb]

@BrMBr thanks for pointing this out. This way I could find out in my case that the app MonitorControl https://github.com/MonitorControl/MonitorControl is also responsible for the problems. As soon as I quit MonitorControl the snapping works as usual.

[tilliwilli]

Just wanted to add here that in my case MacGesture (https://github.com/MacGesture/MacGesture) is also causing the issue to appear. MonitorControl on the other hand causes no problems for me. I'm using RectanglePro 3.0.9, MacGesture 3.2.0 and MonitorControl 4.2.0.

[rxhanson]

Anyone up for trying out another beta?

https://rectangleapp.com/pro/downloads/Rectangle%20Pro%203.0.11.dmg

[FL0R1AN84]

Yes, that version works for me. I've tested it with Quick Shade

and thank you very much for your quick response

[BrMBr]

I confirm it's now working with Quick Shade.

Thanks

[FL0R1AN84]

It only worked for me for a short time. Even with version 3.0.11 I still have problems on my Mac mini and Mac Pro. At least on my Mac Pro I was able to determine that it was partly due to MS Teams and LanguageTool Desktop. I now use Magnet and have now noticed that both of these apps now work excellently. Unfortunately, not with Rectangle Pro.

At least with version 3.0.8. Everything seems to be going better so far. Although, I'm not sure that the issues with MS Teams and LanguageTool weren't there before.

[rxhanson]

@FL0R1AN84, it's likely that Magnet never accounted for the initial macOS issue that caused the switch in how snap by dragging is handled. In v3.0.11, I included a way to revert back to the old behavior prior to v3.0.9 and it can be enabled via this terminal command:

defaults write com.knollsoft.Hookshot systemWideMouseDown -int 1

By reverting back to the old way, you would have the issue where certain tables in macOS and other apps won't respond to clicks properly (only really frustrating if you don't know why it's happening since you can just use your keyboard to change selection).

[ErHaWeb]

I can confirm that it now also works with MonitorControl again.
Thank you!

[Hannnsen]

Are some users also having problems with the BetterDisplay app? It seems I have a similar issue. Does anybody else have the issue that snap doesn't work, but the rest of rectangle works without problems?

[JeanMertz]

At least with version 3.0.8. Everything seems to be going better so far. Although, I'm not sure that the issues with MS Teams and LanguageTool weren't there before.

I can confirm that for me, as soon as I quit LanguageTool, snap areas started working, without even needing to restart the app. I should also note that the related feature "Snap Panel" also didn't work while the Language Tool app was open.

[DerGraeflicheGraf]

At least with version 3.0.8. Everything seems to be going better so far. Although, I'm not sure that the issues with MS Teams and LanguageTool weren't there before.

I can confirm that for me, as soon as I quit LanguageTool, snap areas started working, without even needing to restart the app. I should also note that the related feature "Snap Panel" also didn't work while the Language Tool app was open.

Same. It works with BetterDisplay running.