-
Notifications
You must be signed in to change notification settings - Fork 281
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
Unexpected compound modifier behavior #1436
Comments
You're using the exact same side for each modifier? Same order for pressing the keys? |
yes and yes |
Moreover, the plover-disabled manual combo works irrespective of order (provided the PrtSc is last). And the manual ctrl-alt-PrtSc behavior described is the behavior whether plover is open or not, and whether plover is disabled or enabled. |
Plover has some known issues with Alt modifiers in Windows, specifically with OS-level shortcuts like Alt-Tab. Poster child of a Heisenbug, that one...debugging an issue with focus switch is rather difficult with debuggers that steal focus on breakpoints. |
Alt+tab issue may be #1154 . Try merging the related pull request to see if this issue is also fixed. If it still doesn't work try applying #1410 (comment) too. |
I'm not certain this is a bug, (it could be intended behavior) but it's unexpected, and I'm curious why it occurs.
When pressing the following key combinations with plover output disabled:
alt-PrtSc take a screenshot of the current window
ctrl-alt-PrtSc does the same, presumably because Windows ignores the unnecessary ctrl
When making a plover dictionary entry for these bindings, the latter doesn't work. That is:
{#Alt_L(Print)} takes a screenshot of the current window
{#Control_L(Alt_L(Print))} takes a screenshot of the entire screen, same as {#Print} on its own
The expected behavior would be for the last case to behave exactly the same as ctrl-alt-PrtSc and take a screenshot of the current window.
Operating system and hardware
The text was updated successfully, but these errors were encountered: