The "stuck" part sounds like the X/Y issue I mentioned in other email.
I've saw it in the other button post code path if I set tablet pen to
relative mode. In that path, some X acceleration logic causes some
negative values and does bad things. See related comment in
wcmSendNonPadEvents() for re
On Tue, Apr 5, 2011 at 1:00 PM, Jason Gerecke wrote:
> The prior patch has gestures use button mapping like buttons et.al.,
> but for some reason this results in the cursor being "stuck" at the
> top left of the screen when:
>
> 1) A gesture is performed
> 2) The gesture uses a button with an asso
The prior patch has gestures use button mapping like buttons et.al.,
but for some reason this results in the cursor being "stuck" at the
top left of the screen when:
1) A gesture is performed
2) The gesture uses a button with an associated action
3) The action presses a button but does not release
