-
Show log
Commit
-
Hash : 860cfc03
Author :
Date : 2020-04-05T00:07:57
keymap: don't forget about fallback mappings in xkb_keymap_key_get_mods_for_level() If the active set of modifiers doesn't match any explicit entry of the key type, the resulting level is 0 (i.e. Level 1). Some key types don't explicitly map Level 1, taking advantage of this fallback. Previously, xkb_keymap_key_get_mods_for_level didn't consider this, and only reported masks for explicit mappings. But this causes some glaring omissions, like matching "a" in the "us" keymap returning not results. Since every mask which isn't explicitly mapped falls back to 0, we can't return the all. Almost always the best choice for this is the empty mask, so return that, when applicable. Fixes https://github.com/xkbcommon/libxkbcommon/issues/140. Reported-by: https://github.com/AliKet Signed-off-by: Ran Benita <ran@unusedvar.com>
-
Files
- .gitignore
- atom.c
- buffercomp.c
- common.c
- compose.c
- context.c
- data/
- evdev-scancodes.h
- filecomp.c
- how-to-type.c
- interactive-evdev.c
- interactive-wayland.c
- interactive-x11.c
- keymap.c
- keyseq.c
- keysym.c
- log.c
- print-compiled-keymap.c
- rmlvo-to-kccgst.c
- rmlvo-to-keymap.c
- rules-file-includes.c
- rules-file.c
- rulescomp.c
- state.c
- stringcomp.c
- symbols-leak-test.bash
- test.h
- utf8.c
- x11.c
- x11comp.c
- xkeyboard-config-test.py.in
