<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Double tap not always recognized"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90172#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Double tap not always recognized"
href="https://bugs.freedesktop.org/show_bug.cgi?id=90172">bug 90172</a>
from <span class="vcard"><a class="email" href="mailto:lisec.velimir@gmail.com" title="Velimir Lisec <lisec.velimir@gmail.com>"> <span class="fn">Velimir Lisec</span></a>
</span></b>
<pre>(In reply to Peter Hutterer from <a href="show_bug.cgi?id=90172#c19">comment #19</a>)
<span class="quote">> 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.</span >
Will do.
<span class="quote">> 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.</span >
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>