From 4b69d6f71db973ae402d68fdd80c7b92663b352e Mon Sep 17 00:00:00 2001 From: Ran Benita Date: Sat, 15 Sep 2012 02:09:34 +0300 Subject: 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 --- test/data/keymaps/stringcomp.data | 2 -- 1 file changed, 2 deletions(-) (limited to 'test/data') 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; = 9; = 10; = 11; -- cgit v1.2.3