<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 - RFE: Enable middle-button-drag coexisting with scroll emulation"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106435">bug 106435</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>
<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;">Summary</td>
<td>Enable middle-button-drag coexisting with scroll emulation
</td>
<td>RFE: Enable middle-button-drag coexisting with scroll emulation
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - RFE: Enable middle-button-drag coexisting with scroll emulation"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106435#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - RFE: Enable middle-button-drag coexisting with scroll emulation"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106435">bug 106435</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>No, sorry. This feature is going to be virtually undiscoverable if it's hidden
within libinput and based on timeouts and movement thresholds. The latter is
difficult anyway, especially on trackpoints. We don't really have a notion of
"pixels" because we don't know the screens.
What you want is something that is mutually exclusive. Either you get button
scroll or you get button drag. But it's the same physical interaction from the
POV of the device.
A better solution here would be to move the scroll button to a button you don't
need for dragging. Or use a device that doesn't rely on middle button+drag for
scrolling.
Sorry, not something that I'll add to libinput.</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>