| commit | 2ec571a30c0c3b1a17f6b3631c80d573582f59a1 | |
| author | Petar Kapriš <petarkapris@firemail.cc> | |
| Sat, 17 Jul 2021 22:14:00 +0000 (18 00:14 +0200) | ||
| committer | Hiltjo Posthuma <hiltjo@codemadness.org> | |
| Sun, 18 Jul 2021 09:44:56 +0000 (18 11:44 +0200) | ||
| tree | 236e40db75385e56e30d315cfe65878f556e9e2a | treesnapshot (tar.gz zip) |
| parent | 4536f46cfff50c66a115755def0155d8e246b02f | commitdiff |
Add 14th bit to XK_SWITCH_MOD bitmask
The bits of uint signal in an XKeyEvent which concern the key group (keyboard
layout) are bits 13 and 14, as documented here:
https://www.x.org/releases/X11R7.7/doc/libX11/XKB/xkblib.html#Groups_and_Shift_Levels
In the older version, only bit 13 was marked as part of XK_SWITCH_MOD, this
causes issues for users who have more than two keymaps. the 14th bit is not
in ignoremod, key sequences are not caught by match(), if they switch to a third
or fourth keyboard.
The bits of uint signal in an XKeyEvent which concern the key group (keyboard
layout) are bits 13 and 14, as documented here:
https://www.x.org/releases/X11R7.7/doc/libX11/XKB/xkblib.html#Groups_and_Shift_Levels
In the older version, only bit 13 was marked as part of XK_SWITCH_MOD, this
causes issues for users who have more than two keymaps. the 14th bit is not
in ignoremod, key sequences are not caught by match(), if they switch to a third
or fourth keyboard.
| x.c | diffblobblamehistory |