You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While using qemu I found that snowglobe and sometimes qemu-rdw would inhibit super key and super + key combos from working.
This means I could not move it to another workspace, nor even close it when it stopped responding. Pair the hotkey takeover with it grabbing the cursor, I wound up needing to swap to another TTY just to kill the application.
The text was updated successfully, but these errors were encountered:
So how exactly would you expect to select which shortcuts are supposed to be forwarded to the application and which aren't?
The zwp_keyboard_shortcuts_inhibit_manager_v1 protocol or the zwp_xwayland_keyboard_grab_manager_v1 (which are probably in use by either linked application) are meant to make it possible to fire off e.g super-shortcuts inside the viewer. So I would rather expect them to have some built-in shortcut to lift the grab?
That said we probably could (and should) add a configurable shortcut to lift any inhibits and possibly add an applet to visualize that state (and also provide a cursor-based flow to lift the lock).
I see, I wasn't aware of that protocol. For me, I have always expected super shortcuts to be available for those host to use. I suppose I may have just got lucky with the software I use. I think the solution you presented would be ideal. Editing the title to reflect the state.
Quackdoc
changed the title
[Bug]: Some applications can take over super
[Request]: Allow disabling shortcuts inhibiting
Nov 25, 2024
While using qemu I found that snowglobe and sometimes qemu-rdw would inhibit super key and super + key combos from working.
This means I could not move it to another workspace, nor even close it when it stopped responding. Pair the hotkey takeover with it grabbing the cursor, I wound up needing to swap to another TTY just to kill the application.
The text was updated successfully, but these errors were encountered: