dokutan

> macros are either not applied or are not captured by mouse_m908 --read / mouse_m908 -R - @1nekomata Could you figure that out by applying multiple macros with mouse_m908 and...

@1nekomata I can only guess the reason but the capture doesn't contain a macro, only the normal settings. Maybe binding the macro to a button is required for RDCfg to...

To start adding support would require a capture of the usb communication with the official software and a detailled description of the features the M901 has (number of buttons, minimum/maximum...

Thanks for the lsusb output, the product id is different from the one listed in the readme. I have added it to the generic backend with 4cbbb26d4ddbe80b820472639430edc0bc131d78, in case you...

Please start by posting the output of ``lsusb``

Sounds great, both as a useful thing to have and personal learning experiance (for me at least). And considering that github actions are free for public repos i don't see...

Thanks, i have enabled support for the M909 in the generic backend. I would add a specific backend when more information (buttons, DPI) becomes available.

Hello and thanks, i just saw this issue and had a brief look at the captures. From the official software, that you posted, the USB PID appears to be 0xfc0f,...

I have added a new branch ``m990`` with a M990-specific backend. As it turns out the data layout is different for the M990, this also explains the broken official software....

Thanks for the info, that really helped to get a general understanding of the features. Unfortunately i am now certain that this mouse uses a different data layout (not such...