<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - wl_fixed is not precise enough for high dpi mice"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85715#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - wl_fixed is not precise enough for high dpi mice"
href="https://bugs.freedesktop.org/show_bug.cgi?id=85715">bug 85715</a>
from <span class="vcard"><a class="email" href="mailto:x414e54@linux.com" title="x414e54@linux.com">x414e54@linux.com</a>
</span></b>
<pre>I have added a new bug about direct access to libinput events marshal by the
compositor.
<a class="bz_bug_link
bz_status_NEW "
title="NEW - Raw, HID and Direct libInput Protocol."
href="show_bug.cgi?id=90068">https://bugs.freedesktop.org/show_bug.cgi?id=90068</a>
As you know most games or game apis do not use "relative pointers" they deal
with the HID input APIs directly. The events are sent by the window manager.
Having access to the libinput events (or a similar API) directly will allow
both relative motion events and also allow for high dpi mice. libinput can then
be extended separately of Wayland to allow transmitting dpi, sensitivity,
deadzone information and any anything.
If the compositor is not happy about forwarding the event due to window focus
or a grab then it does not.
This is slightly separate of the confinement and locking issue but definitely
preferably to "relative pointers" as it allows extensibility for 3D and VR
whilst the compositor remains in control.</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>