<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Wacom tablet produces wiggly bent lines when using libinput driver."
href="https://bugs.freedesktop.org/show_bug.cgi?id=99961#c11">Comment # 11</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Wacom tablet produces wiggly bent lines when using libinput driver."
href="https://bugs.freedesktop.org/show_bug.cgi?id=99961">bug 99961</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>afaict so far these jittery lines here are caused by libinput not doing any
coordinate smoothing like the wacom driver does. The sensors aren't that
accurate, so this causes the occasional movement. I have a patchset here that
does the same 4-event averaging that xf86-input-wacom does and it seems to work
fine - the patchset just needs to be tidied up more.
As for which fields to use: it must be driver independent, anything else is a
bug. the valuators have the highest precision but are in device units, the
events_x/y have the pre-formatted coordinates relative to the window. I'd
recommend those anyway because it'll make the wayland integration easier
(wayland only provides the event x/y equivalents).</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>