Cut mouse polling rate in half

[Dotan Cohen]

On Wed, Jun 1, 2011 at 05:37, Karl Auer <kauer at biplane.com.au> wrote:
> There are two items in the dialogue - acceleration and sensitivity. The
> first controls when the mouse goes into overdrive, the second controls
> how fast the mouse cursor moves on screen relative to how fast you move
> the actual device over the mousing surface.
>
> It is *exactly* what Dotan is looking for.
>

Thanks, but I think that you attribute to sensitivity the function
done by acceleration. I wonder what sensitivity does, and if it is in
fact what I need.


> KDE has so many bells and whistles, I'd certainly expect it to have this
> too. Maybe it's just better hidden.
>

Yes, I would expect so too!


> Dotan - try "man xset", under the "mouse" subcommand. It looks to me as
> if it might do what you want with a threshhold of zero, so the
> "acceleration" parameter applies to all mouse movement - e.g. "xset
> mouse 1/2 0". Haven't tried it though.
>

Only acceleration and threshold options, no speed coefficient.


> Also, you may find xinput helps. Use "xinput --list --short" to find out
> what devices you have, then feed that name into "xinput --list-props" to
> find out what twiddlable properties it has, them use "xinput --set-prop
> <whatever>" to set that property.
>

I think that you've found it!
Device Accel Velocity Scaling (259):    10.000000

Playing with this parameter is not intuitive as I expected, but I
might be able to make it work. Thank you! Even better, I think that I
can restrict this to the problematic mouse and not affect the other
one!


> I think you'd have to put these things in a script to run at startup.
> Nice thing about the xinput solution (if it is a solution) is that it
> will apply only to the particular mouse you configure with it - other
> mice will be left alone.
>

Yes. exactly! Thanks Karl!


-- 
Dotan Cohen

http://gibberish.co.il
http://what-is-what.com