Add support for Prime mice #169
Conversation
Hum that's annoying, I have already an implementation for this in the aerox3-wireless branch... Maybe I can merge this part of the branch on Except this ↑ your PR looks great :) |
I had a look at the |
|
The updated |
The 'process_value' function of the 'range' handler is reused by 'multidpi_range'. Separate the actual processing in a different function. This will make it possible in future commits to change the return of 'process_value' for the 'range' handler.
Add support for outputting a value on multiple bytes. The new device option is called 'range_length_byte'.
|
OK I updated the code to use the new |
|
Thank you, the Prime support will be released in the next Rivalcfg version :) |
This adds support for the SteelSeries Prime mice (#166).
Supported features:
What is not supported:
By looking at the SSE3 database, it seems like the Prime and Prime+ support a new color handler. Instead, I was able to reuse the regular
colorhandler by using thecommandandcommand_suffixfields to build a valid packet (but different from my captures). In short, the RGB color value is present twice in the data, at the start and at the end. Sending only at the start also works. But this means supporting the Prime+ will most likely require to correctly implement this new color handler.There were a few changes to the core code, mainly:
rangehandler (new optionrange_length_byte)multidpi_rangehandler