On Wed, May 01, 2013 at 03:47:39PM +0200, Alexander Maret-Huskinson wrote:
> one of our users informed us about a bug in the KDE Wacom KCM which makes it 
> impossible to set keys which require the shift-key to be pressed. It turned 
> out that xsetwacom always sends the unshifted base form of the key, unless 
> you 
> actually include the shift modifier.
> 
> For instance:
> 
> xsetwacom ... set Button 1 "key exclam"
> 
> ... will always send a "1" if you have an english keyboard layout where the 
> "!" is Shift-1.
> 
> However, if you map the button to...
> 
> xsetwacom ... set Button 1 "key +shift exclam -shift"
> 
> ... or ...
> 
> xsetwacom ... set Button 1 "key +shift 1 -shift"
> 
> ... then it will correcly send a "!" key event. The same is true for any key 
> which requires you to press the shift modifier.
> 
> >From my point of view "key exclam" should correctly send a '!', as that is 
> what the user intended. However I'm not sure how this is supposed to work on 
> your side.
> 
> Do you consider this to be a bug or do we have to fix this on our side by 
> translating such keys back to the actual keyboard shortcut?

it's an issue with the way how the wacom driver can submit key events. what
xsetwacom does is find the keycode that has that symbol in the current group
and then configure the driver to send that keycode. hence, 'q' and 'Q' (us)
and 'a' and 'A' (fr) will result in the same keycode being sent. Likewise,
'1' and '!' are the same.

This was a concious decision, though made largely due to the complexity
involved in guessing what modifier key combos are supposed to be pressed
and released for each key. aside from decyphering the XKB configuration some
configuration can be tricky. e.g. on a german keyboard layout the "alt Q"
would not be possible (since AltGr+Q → @) and would have to be decomposed to
"+alt -alt +shift q -shift +alt" (or something like that).
not a likely shortcut, I admit, but I think it shows the problem and
complexity well enough.

xsetwacom's key configuration should thus be seen as "the set and order of
the physical keys pressed". I'll add something along those lines to the man
page. I don't expect this to get fixed anytime soon, sorry.

Cheers,
   Peter




------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to