<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - hwdb: Logitech, Inc. RX 250 Optical Mouse DPI data (older model)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87435#c7">Comment # 7</a>
on <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - hwdb: Logitech, Inc. RX 250 Optical Mouse DPI data (older model)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87435">bug 87435</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>(In reply to Thomas H.P. Andersen from <a href="show_bug.cgi?id=87435#c6">comment #6</a>)
<span class="quote">> That sounds reasonable. I was working on a patch for mouse-dpi-tool to show
> the frequencies in a histogram. If we only really need the max frequency
> then current code is fine. In my testing the mouse would use 142.9Hz ~90% of
> the time. I could not find any specific steps to trigger the higher or lower
> frequencies. I guess the user just has to move the mouse for a while and
> hope we have found the max?</span >
pretty much. I don't know what the devices employ for frequency scaling - is it
lots of little movements, lots of large movements? I honestly don't know. You
can still do the frequency patch if you want though, it may be useful.
<span class="quote">> For all the mice I tested I was able to find an advertised dpi on the
> internet. I just tested that I could get reasonably close to that dpi with
> your tool and then used the advertised value. Does that make sense?</span >
definitely. with high enough dpis a slight erratic movement or measurement
error can quickly result in odd numbers, so if the manufacturer says 1000dpi
and you measure in the 900-1100 range then I'd say go with the advertised one.
There's other factors involved too, if the surface isn't perfect you may not
get the exact reading even if you move the right distance, etc.
<span class="quote">> Nitpick: the tool truncates the frequency when creating the hwdb entry. So
> for 142.9Hz it will use xxx@142.</span >
I didn't think we needed floating point frequencies tbh and I'm still not
convinced that we do. Rounding otoh would be useful I guess.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>