state, map: use keycodes only for the API functions
authorRan Benita <ran234@gmail.com>
Fri, 14 Sep 2012 08:02:12 +0000 (11:02 +0300)
committerRan Benita <ran234@gmail.com>
Fri, 14 Sep 2012 18:09:49 +0000 (21:09 +0300)
commit841f32230af7024dc6a8e254a9dc3304301022c9
treed64c8448ee5f352e13ff42c9b6d0d0bc09b6dcee
parent4d3d2ef004222c4255ae94ed9d58693ccc9dc396
state, map: use keycodes only for the API functions

The policy is now consistent: every API functions which recieves a
keycode should resolve it to an xkb_key first thing, and all the
internal functions use that instead of the keycode.
To facilitate it a bit, we move the KeycodeInRange check to XkbKey
itself, which returns NULL if the keycode is illegal.

Signed-off-by: Ran Benita <ran234@gmail.com>
src/map.c
src/state.c
src/xkb-priv.h