OK, attached is my suggested fix for this.  It fixes messages on X
side for limited cases I've tested so far.

I went a slightly different route then discussed earlier and I reset
past history so an exact value can always be sent.  If you think
touching dev->abs[] values would be rejected from linux kernel then
same basic history framework is needed for +/- 1 work around anyways.

I also fixed an issue bugging me with static variables in same code
but not 100% related to lost data.  It could be submitted separate.

Same basic concepts apply in at least tpc code paths.  If patch is
acceptable, I can help port to other areas of code.

Chris

Attachment: 0001-Fix-for-lost-x-y-pressure-data-in-two-finger-case.patch
Description: Binary data

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Linuxwacom-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel

Reply via email to