From 82f1b72d1314246b252c53cd45011a232db59360 Mon Sep 17 00:00:00 2001 From: Dana Jansens Date: Tue, 9 Feb 2010 21:03:01 -0500 Subject: [PATCH] i learnt what xkb does with the state. use the state from keyrelease events directly, rather than query the state (which is not as accurate!) the xkb state (as opposed to the normally sent compat state) contains extra info like the keyboard group, the pointer buttons, etc. so we can just strip that stuff out. (See section 2.2.2 of the XKB proto document) --- openbox/event.c | 20 +++++++------------- 1 file changed, 7 insertions(+), 13 deletions(-) diff --git a/openbox/event.c b/openbox/event.c index 51cfc658..1e6df48d 100644 --- a/openbox/event.c +++ b/openbox/event.c @@ -274,20 +274,14 @@ static void event_hack_mods(XEvent *e) break; case KeyRelease: #ifdef XKB - /* If XKB is present, then the modifiers are all strange from its - magic. Our X core protocol stuff won't work, so we use this to - find what the modifier state is instead. */ - if (XkbGetState(obt_display, XkbUseCoreKbd, &xkb_state) == Success) - e->xkey.state = - obt_keyboard_only_modmasks(xkb_state.compat_state); - else + /* keep only the keyboard modifiers. xkb includes other things here. + (see XKBProto.pdf document: section 2.2.2) */ + e->xkey.state &= 0xf; #endif - { - e->xkey.state = obt_keyboard_only_modmasks(e->xkey.state); - /* remove from the state the mask of the modifier key being - released, if it is a modifier key being released that is */ - e->xkey.state &= ~obt_keyboard_keycode_to_modmask(e->xkey.keycode); - } + e->xkey.state = obt_keyboard_only_modmasks(e->xkey.state); + /* remove from the state the mask of the modifier key being + released, if it is a modifier key being released that is */ + e->xkey.state &= ~obt_keyboard_keycode_to_modmask(e->xkey.keycode); break; case MotionNotify: e->xmotion.state = obt_keyboard_only_modmasks(e->xmotion.state); -- 2.34.1