On Sun, Jan 23, 2011 at 06:25:45PM +0100, Andrzej Giniewicz wrote: > Hi, > > today I noticed one thing, I tried to set one of buttons to "key super > t" - though when checking it in xev I found out, that the key being > used instead of Super_L is: > > keycode 132 (keysym 0x0, NoSymbol) > > When I use the actual key on keyboard, it is reported as: > > keycode 133 (keysym 0xffeb, Super_L) > > I tried out xsetwacom with verbose option on, and got: > > ... Key map 65515 (132, 'Super_L') [press,release] > ... Key map 116 (28, 't') [press,release] > > what is interesting, is that the keysyb is correct, but the keycode it > got is off by one. Oh, and Super_R works: > > ... Key map 65516 (134, 'Super_R') [press,release] > ... Key map 116 (28, 't') [press,release] > > and in xev I get same result with both button on tablet and key on keyboard: > > keycode 134 (keysym 0xffec, Super_R) > > Any idea how can this be debuged? I'd be happy to help.
iirc, the keycode should just come from Xlib, stepping through get_special_button_map should help you find where the offset is coming from. Cheers, Peter ------------------------------------------------------------------------------ Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! Finally, a world-class log management solution at an even better price-free! Download using promo code Free_Logger_4_Dev2Dev. Offer expires February 28th, so secure your free ArcSight Logger TODAY! http://p.sf.net/sfu/arcsight-sfd2d _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
