-
-
Notifications
You must be signed in to change notification settings - Fork 643
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Holding down modifier key prevents default click behavior #1801
Comments
👍 to this. I have ALT-click+drag to move windows in yadr, and this inhibits ALT-click on, say, menubar items (to show extended menus). It would be awesome to be able to differentiate these. |
Probably best solved as explained in #601 |
I've had similar weird interactions when I set my mouse_modifier to gist here: https://gist.github.com/mattbailey/9429c7691467bf82d64e1900c99fb53b |
Wouldn't it be possible for yabai to capture the click only when the action is dragging (at least for windows move/resize) ? |
It's not quite that simple. "Dragging" in macOS can only take place when a mouse button is held/pressed/down. For "click anywhere" to work, yabai needs to intercept the initial click event that is reported before the drag events begin. The best that I can think of would be to replicate the click if no drag-events occur in between the mouse-down and mouse-up event. |
Thanks! |
New change somehow randomly causes segfaults... Not completely sure why, code looks fine to me, but w/e easy fix. |
I use option as my modifier key, which works fine for the most part. However, when I need to hold down option to click on an item in a context menu (e.g. the finder app's right click menu), the click fails to register. Since the only use case for the modifier keys is holding down click to drag while resizing/moving windows, would it be possible to differentiate clicks from dragging? Thanks.
The text was updated successfully, but these errors were encountered: