Hi Oldřich, I confirm your report. I've reproduced the issue on Xorg 1.7+.
Here is what I did. I tested the issue on two systems with three tablet models: 1. Ubuntu 8.04 with linuxwacom-0.8.5-9 and Xorg 1.4.0 (Graphire 4 and Intuos 3) I issued "xsetwacom set pad button1 "core key c"" instead "xsetwacom set pad button1 "key c", which you did on an Xorg 1.7+. I followed the three steps and I do not see the issue. 2. F12 with the current xf86-input-wacom from the repository and Xorg 1.7.1 (I3 and I4) I issued "xsetwacom set pad button1 "key c"" then followed the three steps on both I3 and I4. I see the issue with both models. The issue is not model dependant. I thought it might be tool type (pad) related. So I tested a Wacom mouse and folllowed the same steps. And I see the issue with type "cursor" too. So, it is likely a keystroke-only issue. However, since it doesn't happen on Xorg 1.4 with linuxwacom, it could also be something in Xorg or xf86-input-wacom. What I also found is if we make a mouse movement (i.e., move the system cursor) after the second step, we do NOT see the issue anymore. This might be why we don't see the issue with other tool types except PAD and CURSOR. It is hard to hold the other tools steady :). We need to trace into the code to see where the issue might be. Please give us some more time to get back to you with a fix. Thank you for your effort in testing the driver for us. Ping 2010/1/2 Oldřich Jedlička <[email protected]>: > Hi, > > I have a problem with PAD buttons (Wacom Intuos 3). When I have one PAD button > configured as a key (`xsetwacom --set "Wacom Intuos3 6x8 pad" Button1 "key c"` > - doesn't matter which one and which key is emitted), the following sequence > moves the cursor to [0, 0] (sometimes to a different x location): > > 1. Press a key on keyboard (doesn't matter which one). > 2. Press a button on PAD that is mapped to some key. > 3. Press a button on PAD that is not mapped (pure button click). > > I've tracked the problem down to XInput. This is what `xinput test -proximity > 12` gives on my system (12 is the ID of the PAD device): > > <pure PAD button click> > proximity in > button press 3 a[0]=2816 a[1]=20449 a[2]=0 a[3]=0 a[4]=0 a[5]=0 > button release 3 a[0]=2816 a[1]=20449 a[2]=0 a[3]=0 a[4]=0 a[5]=0 > proximity out > <now I pressed the key on keyboard> > <mapped PAD button click> > proximity in > key press 50 > key release 50 > proximity out > <pure PAD button click> > proximity in > button press 3 a[0]=0 a[1]=0 a[2]=0 a[3]=0 a[4]=0 a[5]=0 > button release 3 a[0]=0 a[1]=0 a[2]=0 a[3]=0 a[4]=0 a[5]=0 > proximity out > > The position is now a[0]=0 and a[1]=0. I don't know where the problem could > be, but I think it is not in Wacom driver (I've added logging to event posting > and the calls have the same arguments). I would like to at least verify that > I'm not the only one having the same problem. > > Can anyone reproduce the problem? Can anyone point me where to look next (also > source code)? > > Thanks. > > Regards, > Oldrich. ------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Linuxwacom-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
