Tap touches rejected erroneously

[Chase Douglas]

When a touch ends, it is currently removed from a gesture. However, the touch is part of the gesture, it's just no longer active. For example, let's say there is a one touch tap performed:

* Touch 5 begins
* Gesture 3 begins
* Touch 5 ends
* Gesture 3 is recognized as a tap
- Client accepts gesture 3
* Touch 5 is accepted

The current code removes all references to touches in a gesture after the touches have ended. Once touch 5 ends in the example above, the touch is removed from gesture 3. The recognizer then notices that touch 5 is not part of any potential gesture and rejects it erroneously.

The fix requires keeping track of all current touches that make up the gesture, but also keeping track of all touches that were ever part of the gesture too.

[Launchpad Janitor (janitor)]

This bug was fixed in the package utouch-grail - 3.0.3-0ubuntu1

---------------
utouch-grail (3.0.3-0ubuntu1) precise; urgency=low

  [ Daniel d'Andrada ]
  * Updated debian/watch

  [ Stephen M. Webb ]
  * removed udeb package
  * debian/control: added Homepage, Vcs-Bzr, and Vcs-Browser fields

  [ Chase Douglas ]
  * Don't strip binaries in daily builds
  * Re-enable tests, integration tests won't build due to missing xorg-gtest
  * New upstream release.
    - Fix tap gesture ending and then erroneously updating (LP: #949855)
    - Fix premature atomic subscription gestures (LP: #949916)
    - Fix integration test build system (LP: #949933)
    - Fix memory growth of touch start time vector (LP: #955131)
    - Fix atomic tap gestures for very fast taps (LP: #957437)
    - Fix accepted tap gesture touches being rejected (LP: #960438)
 -- Chase Douglas <email address hidden> Wed, 21 Mar 2012 19:29:14 -0700