<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span> changed
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Improve Surface Pro Type Cover 2 support"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99079">bug 99079</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">CC</td>
<td>
</td>
<td>peter.hutterer@who-t.net
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Improve Surface Pro Type Cover 2 support"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99079#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Improve Surface Pro Type Cover 2 support"
href="https://bugs.freedesktop.org/show_bug.cgi?id=99079">bug 99079</a>
from <span class="vcard"><a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> <span class="fn">Peter Hutterer</span></a>
</span></b>
<pre>(In reply to defree from <a href="show_bug.cgi?id=99079#c0">comment #0</a>)
<span class="quote">> ## Problems
>
> Spurious KEY_F23 event when clicking (that is a single click produces mouse
> button + keypress events). (+ pad disabled notification)</span >
if you see KEY_F23 then that's a hardware issue. something isn't initialized
correctly by the kernel, libinput doesn't generate those by itself.
<span class="quote">> Clunky scroll:
> - not always detected
> - take time to start then scroll by one big chunk
>
> No tap and drag feature, this is critical for usability.</span >
is the touchpad detected as a touchpad or just as a mouse-like device? If the
former, you'll have to enable tapping, libinput has it disabled by default.
an evemu-record of a scroll sequence should tell us what's going on there.
<span class="quote">> # Touchscreen
>
> usb-id: 03eb:8209 Atmel Corp.
> libinput-name: Atmel Atmel maXTouch Digitizer
>
> ## Problem
>
> I am not familiar with touchscreen, so maybe the behavior I am about to
> describe is normal and the bug elsewhere.
>
> A sequence for a click is TOUCH_DOWN, TOUCH_FRAME, TOUCH_UP.
> During motion, every TOUCH_MOTION is interleaved with a TOUCH_FRAME.</span >
yeah, that's correct and is the expected behaviour. TOUCH_FRAME is needed to
group frames. either way, short answer here is: touchscreen gestures like
tap-to-click is something that needs to be performed on the client-side, i.e.
in the application. recent GNOME3 should do this but otherwise it depends on
the toolkit.</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>