On Tue, Mar 11, 2014 at 8:35 AM, wiz4rd <thewiz...@arcor.de> wrote:
> Hey guys!
>
> Not sure, if this bug has already been reported – couldn't find a
> solution anyway...
>
> After quite a while I attached my Bamboo CTH-661 (2FG 6x8) again and had
> a look at the Wacom Tablet Control panel in Fedora 20. Trying to assign
> events to the tablet's side buttons resulted in quite some confusion.
>  From a right-handed point-of-view the buttons are react as follows –
> from top to bottom:
>
> Tablet  ->  goes to
>    A    ->     C
>    B    ->     D
>    C    ->  (nothing!)
>    D    ->     A
>
> So, if I wanted the top-most button (A on the tablet) to issue a CTRL+Z
> event I'd have to configure button C inside the control panel
> accordingly, etc.
> Not only that this is quite annoying, tablet button C is renderes
> useless like that.
> Oh and BTW, why can't I assign a simple click event – left, right,
> middle – to those button anymore?
>
> Cheers!
> Marco
>

"Button order chaos" is perhaps a more apt description than you realize...

Unfortunately, Bamboo tablets aren't really well-supported by the
control panel in GNOME at this time. The button mapping issue is
known, and stems from a fundamental difference in how the kernel
presents buttons on a Bamboo tablet. To boil it down to the core,
Bamboo devices end up "skipping" some button numbers, which is not a
situation that libwacom and gnome-control-center can handle
gracefully. I've tinkered in the past with trying to make
xf86-input-wacom present a cleaned-up interface, but because of the
variety of ways that a Bamboo tablet can number its buttons, I wasn't
able to come up with any kind of a solution.

That said, it is possible to work around the issue with some effort.
I've attached a script that does most of the work. You can run it as
`./wacom-gnome-compat.sh <id>` with the ID number of your pad device
reported by xsetwacom. It will re-map the buttons to produce events
that the script can listen for, at which point it will begin asking
you to begin pressing each button or 'q' when finished. Once you've
pressed all the buttons and then hit 'q', it will change the mapping a
second time, this time to a condensed form that should allow GNOME to
use all the buttons. It also prints out the commands that create this
mapping, in case you want to save them e.g. to a startup script.

As for why you can't set the buttons to produce left/middle/right
mouse clicks through the control panel? Unfortunately, the GNOME
developers don't feel that mouse buttons are worthwhile shortcuts and
have resisted attempts to add them in. Worse, because GNOME's
button-mapping magic works by intercepting mouse events sent from our
driver, you can't use xsetwacom to force a specific button to make a
click: the event will just be consumed by GNOME before anything can
see it :(

Jason
---
Now instead of four in the eights place /
you’ve got three, ‘Cause you added one  /
(That is to say, eight) to the two,     /
But you can’t take seven from three,    /
So you look at the sixty-fours....

Attachment: wacom-gnome-compat.sh
Description: Bourne shell script

------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/13534_NeoTech
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to