Repository navigation
Ctrl+Shift release binds fail depending on release order in 0.57.0 #16796
Replies: 2 comments
|
This discussion has been automatically closed. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Since updating to Hyprland 0.57.0, my Ctrl+Shift layout switch no longer works reliably.
I have two release binds. Here they are with the layout-switch command replaced by a notification:
With my layout-switch bindings, I confirmed these results using only left Ctrl and left Shift, with no other keys pressed:
I expect one action for Ctrl+Shift regardless of which key is released first.
Cause
PR #15904 changed
shadowBinds()to check still-held keys as release events.When the first-pressed modifier is released first, it does not match the binding because Hyprland uses the modifier state saved when that key was pressed. Hyprland then suppresses the release bind for the remaining modifier before it is actually released. Neither release runs the action.
Related reports and fixes
There is a related report for mouse release binds in #16709. PR #16788 addresses that case, but its change only skips mouse events, so it does not cover these keyboard bindings.
This comment also mentions that releasing other keys suppresses a release bind. The linked branch addresses that more broadly, but explicitly keeps the old behavior for modifier keys. Ctrl and Shift therefore remain affected.
All reactions