On Wed, May 11, 2011 at 10:29 PM, Jason alavaliant <[email protected]>wrote:
>
>
> On Tue, May 10, 2011 at 12:09 PM, Peter Hutterer <[email protected]
> > wrote:
>
>> On Mon, May 09, 2011 at 08:46:26PM +1200, Jason alavaliant wrote:
>> > Hi, I could use some advise with an issue I've run into with my test
>> users
>> > of wacom-config.
>> >
>> > In some cases my users need to completely disable the touchstrips on the
>> > tablet (so pressing them results in not one single X event).
>> > The best I've come up with so far is mapping the strip to a button 0
>> event
>> > (i.e. xsetwacom set 'Wacom Intuos3 6x8 pad' StripLUp "button +0" which
>> is
>> > what wacom-config is using in it's code currently) however even though
>> > that mapping results in 0 X events if a button is pressed, the
>> touchstrips
>> > when mapped to 'button 0' still seem to emit a 'MotionNotify' event
>> where
>> > the time value goes up (from what I can see with xev) even though no
>> > keypress events are emitted.
>> >
>> > Is there some better / more complete option I can set user pref wise to
>> > completely disable any and all action X wise from the touchstrips? (I
>> > know I could alter the X setup at global level to disable the pad
>> devices
>> > but that also disables the ability to use the buttons on the tablet and
>> it's
>> > not very practical on shared workstations with multiple users logging in
>> > them one after the other (some who would want the touchstrips on and
>> some
>> > who would want them off)).
>>
>> you can't disable the touchstrips. we send the pure strip data because
>> some
>> clients seem to want them, but you can't unmap that part. Fixinig your
>> application seems the better way to work around this bug, or, since you
>> say
>> you can't fix the application, hack up the driver so that the strip values
>> are always 0.
>>
>> Cheers,
>> Peter
>>
>>
> Thanks for the confirmation there is no easy option I'd missed, I'll
> delve into the harder options then.
>
> -J
>
>
I managed to patch the wacom source to disable the MotionNotify events for
pad devices, weirdly though the bug is still occurring even though testing
with xev shows not one single X event being emitted when the strip is
touched. I'm at a bit of a loss as to how that could be as I'm not aware
of any events that xev doesn't show and I don't know how a program can
respond to a device that's not sending any X events. Unless somebody who
knows more about X communication can explain how that could be happening I'm
going to have to talk to autodesk about this since it looks like maya 2010
is doing some pretty weird stuff.
-J
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
