<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 - SMART Board Pen not supported"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104087">bug 104087</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></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - SMART Board Pen not supported"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104087#c20">Comment # 20</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - SMART Board Pen not supported"
href="https://bugs.freedesktop.org/show_bug.cgi?id=104087">bug 104087</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>the wayland protocol is similar to the libinput API and is per-tool. There is
no specific limitation to have only one tool on the surface as long as the
client tracks the proximity events independently.
fwiw, last time I used one of these 10+ years ago the pens were just pens and
the eraser device was a separate entity. Would be interesting to know if that
one sends the right hid reports for BTN_TOOL_RUBBER. At least ont he linked
ifp7000 the eraser is visible in the photo too.
But yeah, the list of issues wrong here means I won't put libinput hacks in to
deal with all this. The device is clearly not working and needs some TLC in the
kernel to be usable. Otherwise we're just making our own lives difficult
because the first person to touch the kernel for this will break any hacks we
put in libinput and then we have a combinatorial explosion of workarounds.
Sorry Thomas, you'll need to look at the kernel and start fixing it there. Once
it has some better support, we can put small hacks in but this is just too
much.</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>