-
-
Notifications
You must be signed in to change notification settings - Fork 626
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
Allow bindings including alt and Windows modifiers without activating menu bar/Start Menu #3472
Comments
Comment 1 by jteh on 2013-08-26 06:09 |
Comment 2 by Michael Curran <mick@... on 2013-08-27 02:37
|
Comment 4 by James Teh <jamie@... on 2013-08-27 06:47
|
Comment 5 by jteh on 2013-08-27 06:51 |
Comment 6 by Michael Curran <mick@... on 2013-08-28 02:33
Changes:
|
Comment 7 by Michael Curran <mick@... on 2013-09-12 01:38
Changes:
|
Comment 8 by mdcurran on 2013-09-12 01:38 |
Comment 9 by Michael Curran <mick@... on 2014-07-18 00:33
|
Reported by jteh on 2013-08-26 04:20
If you bind a keyboard gesture which uses the alt and/or Windows modifiers, the menu bar or Start Menu will often appear when the key is released. This is because we intercept the main key, so Windows doesn't know that Windows/alt was consumed and so acts as if the modifier was pressed alone. Unfortunately, this means that alt/Windows can't really be used, so we lose a great deal of possible key bindings.
RegisterHotKey won't work for us because of the extremely dynamic nature of our bindings and because it can't handle the NVDA key. Trapping the alt and Windows keys completely and sending them ourselves as necessary would work, but it may interfere with other apps and it completely breaks alt/Windows plus mouse dragging.
AutoHotkey gets around this by sending the control key before the modifier release is passed to Windows. As this might trigger undesired behaviour in rare cases, another alternative is to send a vk code of 0xFF which should be ignored. However, brief experimentation suggests this doesn't stop the Windows key from activating the Start Menu.
The text was updated successfully, but these errors were encountered: