Peter Samuelson wrote: > Package: lomoco > Version: 1.0beta1+1.0-4 > > The -m, -h, -g flags do not work with mice that don't support those > resolutions, but there is no indication of failure: > > $ lomoco -m > 001.003: 046d:c00e Wheel Mouse Optical (M-BJ58) Caps: RES > Resolution set to 1200 cpi > > $ lomoco -i > 001.003: 046d:c00e Wheel Mouse Optical (M-BJ58) Caps: RES > Resolution (RES): 400 cpi > USB Mouse Polling Interval: 10ms > > It would be useful for -m/-h/-g to query the mouse after setting the > resolution, to see whether it succeeded.
There is much more which should be done and we need a rewrite. Currently
I'm trying to get informations about the new mice which use the second
HID device for configuration.
I wasn't able to reverse engineer the protocol.
I want to create a library liblomoco and a commandline tool lomoco. So
you can use liblomoco in other projects, KDE for example)
>
> A related wishlist item: lomoco -i should tell me what resolutions are
> supported on each of my mice. I don't know if this can be done by
> querying the mouse, or if a hard-coded lookup table should be used.
> But in any case, I'd appreciate "Caps: RES 800 1200" or whatever,
> instead of just "Caps: RES".
This could be done with a new structure which defines the hightest and
lowest resolution and the steps between them.
MX510:
low: 400
high: 800
step: 400
G5:
low: 400
high: 2000
step: 50
There is no check what mouse is connected to a receiver. Often Logitech
uses a receiver for different mice and this is a problem of the current
lomoco. We don't detect it.
I know there are no updates and it looks like the project is dead but I
want to support the new mice with the new version too. I hope to get in
contact with Logitech soon.
-- andreas
--
http://www.linux-gamers.net - your online gaming resource
signature.asc
Description: OpenPGP digital signature
