<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_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Default resolution fallback for libinput missing / devices changing resolution"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105342">bug 105342</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;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</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_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Default resolution fallback for libinput missing / devices changing resolution"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105342#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Default resolution fallback for libinput missing / devices changing resolution"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105342">bug 105342</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>libinput makes a few promises in its API that make using libinput more useful.
One of these is that some calls return the data in mm - and for that we need to
know the resolution of the tablet. There is no good reason for a tablet to not
have a resolution set. We have the 60-evdev.hwdb now for physical devices that
lack it (or have wrong values set) and in the case of networked tablets like
this - just set it in the software that creates the tablet. This is a
one-liner to set in gfxtablet but it's many lines of code, APIs set in stone,
required configuration interfaces, etc. in libinput. Not a good trade-off, tbh.
There is no default resolution, some touchpads have 12 units/mm some tablets
have hundreds of units/mm.
The 'outside expected range' is just a warning and indicates that the ranges
are set up wrongly. For physical devices this would require a 60-evdev.hwdb
fix, but in this case it's a uinput device and can just be fixed in code there.
<span class="quote">> I think libinput should add devices anyway with a default resolution and
> provide a user interface to change resolutions on the fly, e.g. to change
> between different android devices.</span >
config interfaces in libinput are difficult. libinput has no GUI, so it relies
on the caller to implement any actual user-facing bits. which means
implementing it in gnome, kde, enlightenment, xorg, ... unless there's a
reasonable chance this will happen, there's little point in putting it in
libinput. And quite frankly, libinput right now is not set up to deal with
changing resolution on the fly so the best you could do would be to have it as
static configuration on startup. But this is all moot because the other side of
the device is a uinput device and there's really no excuse for sending garbage
data here.
sorry, definitely a wontfix on the libinput side, this needs to be addressed in
gfxtablet.</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>