On Fri, May 13, 2011 at 10:21:52PM +1200, Jason alavaliant wrote: > 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.
X sends three different events for each device event. a core event, an XI 1.x event and an XI2 event. xev only listens to core events, I expect maya listens to XI 1.x events. though we don't filter properly in the server so you should still see core events for every XI event, even if the coordinates don't change in the core events. note that the one → three event conversion is done in the server, we only ever post one event to the server. either way, all the button events have the coordinates of the touchstrips included, so you would still see the movement whenever a button event comes through. I suspect this may be the issue you're seeing. Cheers, Peter ------------------------------------------------------------------------------ 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
