https://bugs.freedesktop.org/show_bug.cgi?id=96225
--- Comment #13 from Paviluf <[email protected]> ---
(In reply to Peter Hutterer from comment #12)
> ok, the systemd patch got merged so the DPI information should be correct
> now.
Thank you very much but I think we maybe have made a mistake. The 1200dpi value
I got was due to an "old" hwdb. I just saw that the mouse dpi was recently set
to 1000dpi@125
https://github.com/whot/systemd/commit/62f6eed416e3f4a473e3f2b39dc5457284e34f58
and after some more research I always found that the M500 is a 1000dpi mouse
and advertised as such :
https://secure.logitech.com/en-us/product/corded-mouse-m500
http://www.logitech.fr/fr-fr/product/corded-mouse-m500
...
There is only one and only one link that say it's a 1100dpi mouse and
furthermore it says max: 1100dpi :
http://support.logitech.com/en_us/product/corded-mouse-m500
I also find it more pleasant to use at 1000dpi even if the pointer acceleration
is not optimal for now as you said. I don't know how precise is mouse-dpi-tool
but maybe we should revert back the patch ? What do you think ? By the way the
title of the patch is wrong it's the M500 mouse not the MX500 ;-)
> The next problem is that it's still not good enough according to comment 9,
> so that's another bug about pointer acceleration not being good enough.
> unfortunately I still have (at least) one big feature on my slate before I
> can look at pointer acceleration, so this won't be looked at until after
> libinput 1.4, sorry.
At 1000dpi@125 the pointer acceleration is good enough for now, so it's not
really a problem.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
_______________________________________________
wayland-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
