On Mon, Dec 14, 2009 at 08:38:10AM +0100, Oldrich Jedlicka wrote: > > can you give me some more info what exactly you're referring to here? you've > > assigned the button to be "Shift"? is that correct? > > Exactly. Assign a "Shift" key functionality to a button (button > press=shift pressed,button release=shift released). I was using also the > "Ctrl" key for another button. I think it would be sufficient to release > all "forgetten" pressed keys automatically (in reversed order), when the > button is released - that would sanitise the user's input too. >
just verifying: your commandline argument was xsetwacom --set "Device Name" "Button1" "key shift" if so, the patches on my devel branch should fix this issue http://cgit.freedesktop.org/~whot/xf86-input-wacom/log/?h=devel it'd be great if you could give this a test. > > > I have also difficulties double-clicking Button 3, because it > > > freezes any mouse/tablet clicks (no buttons react) until some key is > > > pressed. > > > > just double-clicking the physical button or assigning doubleclick to it? > > Just double-click (Button 3) without any assigned functonality - just a > pure button. I've tried it with tracing enabled, but I didn't see any > difference from single click, only no mouse clicks accepted afterwards > (also from normal mouse) - until the keyboard's key is pressed. > > I wanted to have a look at it during weekend, but I didn't have any free time > for that... I can't reproduce this here, doubleclicks go through normally, without any issues. Not sure what happens there. Cheers, Peter ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
