diff options
author | Ran Benita <ran234@gmail.com> | 2012-09-15 02:09:34 +0300 |
---|---|---|
committer | Ran Benita <ran234@gmail.com> | 2012-09-15 02:09:34 +0300 |
commit | 4b69d6f71db973ae402d68fdd80c7b92663b352e (patch) | |
tree | 5539232f18e86f4ad2a5df60fb47c331b3bee93a /test/data | |
parent | c53122cb96d529168eff3934eeb6333636d019f6 (diff) |
keycodes: ignore explicit minimum/maximum statements
These statements are pretty pointless for us; we don't restrict keycodes
like X does, and if someone writes e.g. maximum = 255 but only has 100
keys, we currently happily alloc all those empty keys. xkbcomp already
handles the case when these statements aren't given, and uses a computed
min/max instead. We should just always use that.
(Of course since keycodes/evdev currently uses almost all of the
keycodes in the range it declares, including 255, this doesn't save any
memory for the common user right now).
Signed-off-by: Ran Benita <ran234@gmail.com>
Diffstat (limited to 'test/data')
-rw-r--r-- | test/data/keymaps/stringcomp.data | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/test/data/keymaps/stringcomp.data b/test/data/keymaps/stringcomp.data index 6d2f3e6..d463655 100644 --- a/test/data/keymaps/stringcomp.data +++ b/test/data/keymaps/stringcomp.data @@ -1,7 +1,5 @@ xkb_keymap { xkb_keycodes "evdev_aliases(qwerty)" { - minimum = 8; - maximum = 255; <ESC> = 9; <AE01> = 10; <AE02> = 11; |