Discard tapping even when there are zero events between down and up

The current logic assumes there will be at least one frame with
between touch up and touch down or the tap will not be properly
timed out. Fixed with this patch.

Reported-by: Chase Douglas <chase.douglas@canonical.com>
Signed-off-by: Henrik Rydberg <rydberg@euromail.se>

1 files changed, 1 insertions, 1 deletions

diff --git a/src/gestures-tapping.c b/src/gestures-tapping.c
index fe7b7fe..b2acae8 100644
--- a/src/gestures-tapping.c
+++ b/src/gestures-tapping.c
@@ -67,7 +67,7 @@ int gru_tapping(struct grail *ge,
                 int x = state->prop[GRAIL_PROP_TAP_X];
                 int y = state->prop[GRAIL_PROP_TAP_Y];
                 int t = move->time - state->start;
-                if (t < TAP_MIN_GAP_MS) {
+                if (t < TAP_MIN_GAP_MS || t > move->fm[FM_X].bar_ms) {
                         gin_gid_discard(ge, state->gid);
                         state->ntouch = move->ntouch;
                         state->active = 0;