<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 - Expose an acceleration setting"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101140">bug 101140</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;">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>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Expose an acceleration setting"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101140#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - Expose an acceleration setting"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101140">bug 101140</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>Sorry, still closing this as WONTFIX, for a couple of reasons:
* the reason this still isn't better is ETIME on my side (and lack of hardware
that's affected by this). [1]
* Apple gets away with it because it's good enough - and this is the point,
isn't it? We have a lot of device-specific code, there's not point having
config options that everyone has to tweak individually when we can just make it
good enough on whole categories or model series at a time
* "acceleration" has very little meaning - what exact factor do you want to
expose?
* once we expose that factor, we're locked into the *algorithm*, because for
any change now we have to figure out how not to break that configuration
So right now, adding that config option has only downsides for the long-term
maintenance efforts.
[1] I pretty much only hear calls for "give me a config option" (which really
means: "a magic number that works for me on my hardware") , but apparently it's
not bad enough for anyone to spend time investigating the cause and finding a
proper solution. Most of the time when I provide branches to test, I get
crickets and tumbleweeds, so my motivation in general is a tad low to work on
this. And my motivation to expose a config option just to get abused whenever
it changes in the future is zero.</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>