-
Show log
Commit
-
Hash : c4f4ba41
Author :
Date : 2025-06-23T18:15:18
state: Fix modifier and group latch Prior to this commit, the sequences: - 1. latch A ↓ 2. latch B ↓ 3. latch B ↑ 4. latch A ↑ - 1. latch A ↓ 2. latch B ↓ 3. latch A ↑ 4. latch B ↑ would result in only B being latched, because the XKB protocol specifies that latches are triggered only if keys are *sequentially* tapped, i.e. a strict sequence of press and release of each key. It seems an unnecessary limitation: - `SlowKeys` and `XkbAX_TwoKeys` are the proper accessibility features to control accidental key presses, not latches nor `StickyKeys`. - Latches are also used outside their original accessibility role. A user may activate multiple latch keys simultaneously: - same hand: two latch keys being close to each other; - different hand: two keys being activated independently. Changed the latching behavior so that the rules used to break a latch are the same than those used to prevent it. Depressing and releasing two latching keys simultaneously will now activate both latches, as expected. Since this is a breaking change, it is enabled only by the keymap format `XKB_KEYMAP_FORMAT_TEXT_V2`.
-
Files
- atom.c
- buffercomp.c
- common.c
- compose-iter.c
- compose-iter.h
- compose.c
- context.c
- data/
- evdev-scancodes.h
- external_xkb_compilers.h
- filecomp.c
- keymap.c
- keyseq.c
- keysym-case-mapping.h
- keysym-case-mapping.h.jinja
- keysym-unicode.c
- keysym.c
- keysym.h
- keysym.h.jinja
- log.c
- merge_modes.c.jinja
- meson_test.map
- messages.c
- modifiers.c
- registry.c
- rules-file-includes.c
- rules-file.c
- rulescomp.c
- state.c
- stringcomp.c
- symbols-leak-test.py
- test-keysym.py
- test.h
- tool-option-parsing.py
- utf8.c
- utils-text.c
- utils-text.h
- utils.c
- x11.c
- x11comp.c
- xkeyboard-config-test.py.in
- xvfb-wrapper.c
- xvfb-wrapper.h
