[Wayland-bugs] [Bug 90172] Double tap not always recognized

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Apr 30 03:32:29 PDT 2015


https://bugs.freedesktop.org/show_bug.cgi?id=90172

--- Comment #20 from Velimir Lisec <lisec.velimir at gmail.com> ---
(In reply to Peter Hutterer from comment #19)
> Not a bad idea re:tap to end drag timeout and increasing that timeout in
> general, please file that as separate bugs though, it's too hard to keep
> track of everything otherwise.

Will do.

> true but that assumes no delay whatsoever. depending on what the system is
> up to, there can be a delay between the timer triggering and us actually
> processing the event. Which is, I think, the reason you had a 200ms delay in
> one of your recordings. And note that you labelled that recording as "normal
> speed", shortening the timeout would've missed the first tap. So for
> double-tap I think a longer + slightly shorter combination may be better.

But what I don't understand is why was the tap from that recording recognized?
Because DEFAULT_TAP_TIMEOUT was set to 180 ms, if the delay is 200 ms, it
shouldn't have been recognized as a tap, but as a pointer move.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20150430/9a96ba1d/attachment.html>


More information about the wayland-bugs mailing list