mirrors/labwc
1
0
Fork 0
mirror of https://github.com/labwc/labwc.git synced 2025-10-29 05:40:24 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

labwc-config(5): describe how keys are processed

Browse source 
...when matching against keybinds.

Copied from:

63dc609085/src/input/keyboard.c (L215-L238)
This commit is contained in:
Johan Malm 2024-12-16 20:13:58 +00:00 • committed by Johan Malm
parent 63dc609085
commit 8863672b1f
1 changed files with 19 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

19
docs/labwc-config.5.scd
View file

@ -589,6 +589,25 @@ extending outward from the snapped edge.
packaged in a lot of distributions and can be used to view all available
keynames.
When matching against keybinds, input keys are processed in the
following order of precedence:
- Keycodes of physical keys (except if keybind is layoutDependent)
- Translated keysyms taking into account modifiers (so if Shift+1 were
pressed on a us keyboard, the keysym would be '!')
- Raw keysyms ignoring modifiers such as shift (so in the above example
the keysym would just be '1')
The reasons for this approach are:
- To make keybinds keyboard-layout agnostic (by checking keycodes before
keysyms). This means that in a multi-layout situation, keybinds work
regardless of which layout is active at the time of the key-press.
- To support keybinds relating to keysyms that are only available in a
particular layout, for example å, ä and ö.
- To support keybinds that are only valid with a modifier, for example
the numpad keys with NumLock enabled: KP_x. These would only be
matched by the translated keysyms.
- To support keybinds such as `S-1` (by checking raw keysyms).
*layoutDependent* [yes|no]
Make this specific keybind depend on the currently active keyboard
layout. If enabled, a keybind using a key which does not exist in