input: Add support for keyboard shortcuts inhibit

Adding support for the keyboard shortcuts inhibit protocol allows remote
desktop and virtualisation software to receive all keyboard input in
order to pass it through to their clients so users can fully interact
the their remote/virtual session. The software usually provides its own
key combination to release its "grab" to all keyboard input. The
inhibitor can be deactivated by the user by removing focus from the
surface using another input device such as the pointer.

Use support for the procotol in wlroots to add support to sway. Extend
the input manager with handlers for inhibitor creation and destruction
and appropriate bookkeeping. Attach the inhibitors to the seats they
apply to to avoid having to search the list of all currently existing
inhibitors on every keystroke and passing the inhibitor manager around.
Add a helper function to retrieve the inhibitor applying to the
currently focused surface of a seat, if one exists.

Extend bindsym with a flag for bindings that should be processed even if
an inhibitor is active. Conversely this disables all normal shortcuts if
an inhibitor is found for the currently focused surface in
keyboard::handle_key_event() since they don't have that flag set. Use
above helper function to determine if an inhibitor exists for the
surface that would eventually receive input.

Signed-off-by: Michael Weiser <michael.weiser@gmx.de>

1 files changed, 8 insertions, 0 deletions

diff --git a/sway/sway.5.scd b/sway/sway.5.scd
index b8b838ab..a2c74e70 100644
--- a/sway/sway.5.scd
+++ b/sway/sway.5.scd
@@ -374,6 +374,14 @@ runtime.
         and one has both _--input-device_ and _--locked_ and the other has neither,
         the former will be preferred even when unlocked.
 
+        Unless the flag _--inhibited_ is set, the command will not be run when
+        a keyboard shortcuts inhibitor is active for the currently focused
+        window. Such inhibitors are usually requested by remote desktop and
+        virtualization software to enable the user to send keyboard shortcuts
+        to the remote or virtual session. The _--inhibited_ flag allows to
+        define bindings which will be exempt from pass-through to such
+        software. The same preference logic as for _--locked_ applies.
+
         Bindings to keysyms are layout-dependent. This can be changed with the
         _--to-code_ flag. In this case, the keysyms will be translated into the
         corresponding keycodes in the first configured layout.