Bug: Cursor stuck when using mouse button to trigger Window Throw

[jerryhcooke]

MacOS 12.3.1 Rectangle Pro v2.4

I can trigger Window Throw just fine with a keyboard shortcut or trackpad gesture, but when I try to map a mouse button I find that it frequently appears to stick the cursor to that point on the screen, only releasing when I hit ⌥

This occurs regardless of the mouse button I use as trigger and irrespective of the keyboard trigger set.

I'm using a Logitech MX Master 3 without Options+ installed and any other mouse controlling software disabled.

[rxhanson]

Thanks for reporting! I suspect there's some macOS strangeness with the way Rectangle Pro is managing the mouse clicks. I'll plan on digging into this for the next release.

[rxhanson]

Sorry for the delay. I did take a look at this for the most recent release, but was unable to come up with anything conclusive as to why this might be happening for you. I don't have an MX Master 3 to test with, so I'm unsure if it is something hardware specific. There is some seemingly delicate behavior with preventing clicks from propagating in macOS, which I suspect would be at the root of this issue. An alternate way to handle this would be to allow clicks to propagate through. The reason I don't do this by default is because buttons 3 and 4 will execute forward and back in Chrome and there's no way to turn that off. Therefore, the only way to get consistent behavior regardless of other applications is to prevent the clicks from propagating. If this appears to be a common issue, and users don't mind the clicks propagating (say if you don't use an app like Chrome and/or buttons 4/5), then I don't mind adding at the very least a terminal command flag for allowing the clicks to propagate if that fixes it.

[tilliwilli]

I'm having exactly the same issue with my Corsair Harpoon, and I just recently found that having "Easy Move + Resize" (https://github.com/dmarcotte/easy-move-resize) running at the same time as having Rectangle Pro Window Throw configured to use any mouse button causes this. Removing the mouse button mapping from Rectangle Pro fixes the issue.

Maybe it has something to do with how the Accessibility API is used by both apps?

PS: So this is also kind of related to https://github.com/rxhanson/RectanglePro-Community/issues/67, since if that was implemented, I could just stop using Easy Move + Resize :) I'm usually using the middle mouse button for resizing anyway, so for me it would not hurt if it wasn't working with the right mouse button.