Re: [Linuxwacom-discuss] xsetwacom not working with keyboard switcher KDE

[Jason G. <kil...@gm...>]

On Mon, Jan 19, 2015 at 3:40 PM, Jason Gerecke <kil...@gm...> wrote:
> On 1/16/2015 12:01 AM, Knapp wrote:
>
> On Mon, Jan 12, 2015 at 11:39 PM, Jason Gerecke <kil...@gm...>
> wrote:
>>
>> On Fri, Jan 9, 2015 at 12:01 AM, Knapp <mag...@gm...> wrote:
>> > Hello,
>> > When I try in input a change to the pad key, it will not work. It sees
>> > different keys that what is put in. (if you need more please let me
>> > know! and Thanks!)
>> > As an example
>> >
>> > douglas@Frog ~ $ xsetwacom -V
>> > 0.24.0
>> >
>> > douglas@Frog ~ $ xsetwacom set "Wacom Intuos PT M Pad pad" Button 1
>> > "key a b c d e f g h i j k l m n o p q r s t u v w x y z"
>> >
>> > douglas@Frog ~ $ axje.uidchtnmbrl'poygk,q;f
>> >
>> > Now I switch to the German keyboard away from the USA dvorak one.
>> >
>> > douglas@Frog ~ $ abcdefghijklmnopqrstuvwxyz
>> >
>> Odd, but understandable. This is what would happen if xsetwacom though
>> the German layout were active when you set the buttons. The keys 'a',
>> 'b', 'c', etc. on a German layout correspond to the keys 'a', 'x',
>> 'j', etc. on a Dvorak layout.
>>
>> > douglas@Frog ~ $ xsetwacom set "Wacom Intuos PT M Pad pad" Button 1
>> > "key a b c d e f g h i j k l m n o p q r s t u v w x y z"
>> >
>> > douglas@Frog ~ $ abidezuhijkpmlorqrstuvwxtz
>> This makes no sense at all. In some cases, it seems to be looking at a
>> German layout (e.g. the 'b' key sends a German 'b') while in others it
>> seems to be looking at a Dvorak layout (e.g. the 'c' key sends a
>> Dvorak 'c' [which, since German is active, comes up as 'i']).
>>
>> > switch back the other way
>> > douglas@Frog ~ $ axce.fgdchtlmnrp'poygk,qyf
>> >
>> This makes sense again: if 'abidezuhijkpmlorqrstuvwxtz' were typed on
>> a German keyboard set to a Dvorak layout, 'axce.fgdchtlmnrp'poygk,qyf'
>> is what you'd expect to appear on the screen.
>>
>> > I am running a fully updated Sabayon KDE with  a CTH-680 pad.
>> >
>> > My xorg.conf
>> >
>> > [SNIPPED]
>> >
>> > Section "ServerLayout"
>> >     Identifier   "Main Layout"
>> >     Screen 0    "Screen 0"
>> >     InputDevice "stylus" "SendCoreEvents"
>> >     InputDevice "eraser" "SendCoreEvents"
>> >     InputDevice "cursor" "SendCoreEvents"
>> >     InputDevice "touch"  "SendCoreEVents"
>> >     InputDevice "pad"
>> I doubt it'd make a difference, but try adding "SendCoreEvents" to the
>> pad device as well.
>
>
> Done.
>
>>
>>
>>
>> > EndSection
>> >
>> > [SNIPPED]
>> >
>> > Section "InputDevice"
>> > Identifier "pad"
>> > Driver "wacom"
>> > Option "Device" "/dev/input/wacom" # USB ONLY
>> > Option "Type" "pad"
>> > Option "USB" "on" # USB ONLY
>> > #     Setting up buttons
>> > Option "Button1" "1"
>> > Option "Button2" "2"
>> > Option "Button3" "key d o u g"
>> The xorg.conf file can only map buttons to other buttons. To have keys
>> be sent, you'll need to use xsetwacom or another tool.
>>
> Yes, I thought so but xsetwacom does give back key codes when you tell it to
> output xorg.conf stuff. Anyway I was just testing here and it did not work.
> I set this back to normal that same day.
>
>>
>> > Option "Button4" "4"
>> > EndSection
>> >
>> > --
>> > Douglas E Knapp
>> >
>> > Creative Commons Film Group, Helping people make open source movies
>> > with open source software!
>> > http://douglas.bespin.org/CommonsFilmGroup/phpBB3/index.php
>> >
>> > Massage in Gelsenkirchen-Buer:
>> > http://douglas.bespin.org/tcm/ztab1.htm
>> > Please link to me and trade links with me!
>> >
>> > Open Source Sci-Fi mmoRPG Game project.
>> > http://sf-journey-creations.wikispot.org/Front_Page
>> > http://code.google.com/p/perspectiveproject/
>> >
>>
>> I'm at a loss to explain what is going on. Could you run `xkbcomp
>> $DISPLAY /tmp/layout.xkb` for me and then attach /tmp/layout.xkb?
>> Also, could you try applying the two patches contained in the bug at
>> [1] and compiling/installing the driver from source?
>
>
> If I find the time for it. I have a big birthday party this weekend.
> I have included the output. The first time is with the dv keyboard and the
> second is with the German. I had no idea if this would change anything but
> it was easy to do.
>
>>
>> They might have
>> an impact on the keycodes that xsetwacom finds in your particular
>> case.
>>
>> [1]: http://sourceforge.net/p/linuxwacom/bugs/269/
>>
>> 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....
>
>
> Thanks for the help.
> Any pointers as to how to compile it? I have not done that sort of thing for
> many years.
>
> --
> Douglas E Knapp
>
> Creative Commons Film Group, Helping people make open source movies
> with open source software!
> http://douglas.bespin.org/CommonsFilmGroup/phpBB3/index.php
>
> Massage in Gelsenkirchen-Buer:
> http://douglas.bespin.org/tcm/ztab1.htm
> Please link to me and trade links with me!
>
> Open Source Sci-Fi mmoRPG Game project.
> http://sf-journey-creations.wikispot.org/Front_Page
> http://code.google.com/p/perspectiveproject/
>
>
> Well, I've taken a look at the files you've provided and it still isn't
> making any sense. Even having XKB use them as my own keyboard layout doesn't
> result in the issues that you're seeing. The 'xsetwacom set' always works as
> expected: it sends the keycodes corresponding to 'a' through 'z' in whatever
> layout was active when it was run. I was neither able to reproduce the first
> issue (xsetwacom using keycodes from the German layout even though Dvorak is
> active) nor the second (xsetwacom sporadically switching between layouts for
> different keys).
>
> Instructions on how to compile and install the driver are available at [1].
> The patch I mentioned is already in our git repository, so I'd recommend
> "building from git" instead of from the tarball. Let me know when you've
> been able to successfully compile and install from source.
>
> [1]: http://linuxwacom.sourceforge.net/wiki/index.php/Xf86-input-wacom
>
> 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....

Have you had a chance to try compiling and installing from git?
Another keyboard layout related issue [1] was just posted to our bug
tracker, and I wonder if its at all related to the issue that you're
having (or the issue I mentioned earlier).

[1]: http://sourceforge.net/p/linuxwacom/bugs/274/

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....