Window snapping invoked unexpectedly by triggers

Bug Reports
1

Describe the bug:
Using the action "Move Mouse to Position" and then invoking Mission Control also sporadically causes Window Snapping. The snap preview appears, and clicking anywhere on the screen will initiate the snap (unless I re-run the action an arbitrary amount of times until the preview goes away). I can't figure out why it's happening and I haven't determined how to reliably reproduce it.

I am using a modified version of the macro described here:
SCR-20230309-oma

but I have also tried it with a macOS hot corner defined to invoke Mission Control:
SCR-20230309-odw
(a separate issue, maybe for a separate thread, is that sometimes CMD Key Up wouldn't work, leading me to think the macro failed at some point before that action)

I love BetterTouchTool, thanks for everything!
Let me know if I can provide any more useful information.

Affected input device:
Normal mouse

Screenshots:
Screenshots not applicable, I will provide video if requested.

Device information:

  • Type of Mac: 2021 14" Macbook Pro (and 2014 15" Macbook Pro)
  • macOS version: 12.6 Monterey (and 11.7.4 Big Sur)
  • BetterTouchTool version: 4.065

Additional information:
I also tried disabling Window Snapping "to top" and using Moom's equivalent feature, but I still wanted to rely on the "Delay Mission Control when dragging windows to the top" feature (which seems to prevent the mouse cursor from moving too far up?) and it seems that isn't active unless "Snap to top" is active.

2

Minor update:

I've migrated the "move mouse and invoke Mission Control" functionality out of BetterTouchTool entirely, moving it to Keyboard Maestro.
I'm still using BetterTouchTool's window snapping feature (best-in-class!).

This setup has reduced the frequency of the issue from a few times per hour down to a few times per week.

3

A comment on your second problem. Someone here once suggested to set up the action "cmd Key Up" twice. No idea if this helps in your case, but it can't hurt. The key cannot be more than up. :smirk: