Keybinding (Re: KDE system guard)

Martijn Klingens klingens at kde.org
Wed Oct 12 08:48:47 BST 2005


On Tuesday 11 October 2005 23:10, Martijn Klingens wrote:
> > Make sure that key is bound on X to something useful
> > and not a modifier.
>
> xev says:
>
> ------------------
> KeyPress event, serial 28, synthetic NO, window 0x3e00001,
>     root 0x3f, subw 0x0, time 13258764, (80,102), root:(911,129),
>     state 0x0, keycode 117 (keysym 0xff20, Multi_key), same_screen YES,
>     XKeysymToKeycode returns keycode: 113
>     XLookupString gives 0 bytes:
>     XmbLookupString gives 0 bytes:
>     XFilterEvent returns: False
>
> KeyRelease event, serial 31, synthetic NO, window 0x3e00001,
>     root 0x3f, subw 0x0, time 13258942, (80,102), root:(911,129),
>     state 0x0, keycode 117 (keysym 0xff20, Multi_key), same_screen YES,
>     XKeysymToKeycode returns keycode: 113
>     XLookupString gives 0 bytes:
> ------------------
>
> That's on my laptop-with-broken-keymaps though, will verify at work
> tomorrow with suse 9.2.

Just checked, it's the same keycode/keysym at work.

Come to think of it, that's strange, since here menu is bound to compose. 
Somehow I never got *exactly* the same kxkb setup working at home with SuSE 
9.1.

I suggest to treat meta-menu as a problem with my setup. If you can help with 
the other meta-combinations that I listed you're more than welcome though.

-- 
Martijn




More information about the kde-core-devel mailing list