mouse_m908 icon indicating copy to clipboard operation
mouse_m908 copied to clipboard

Saftey Feature Request

Open BloodBlight opened this issue 2 years ago • 5 comments

I was a dummy and fat fingered a command and sent the "example_m908.ini" to my M612.

This ended with a mouse that would not move left or right. Ops!

So, I tried re-sending the "generic" example, no help, have a second mouse, captured its config and sent it, no good.

So, found a Windowz box and fixed it there.

Cool.

But on to the feature request. Add a list of "known good" USB IDs and/or the ID that the configuration was captured from. Then if the devices ID isn't in that list, prompt the user with a warning before proceeding.

BloodBlight avatar Jan 31 '24 21:01 BloodBlight

I understand how this can be a problem in some cases, but would think that this problem can be avoided by keeping the personal config in an appropriate location (i.e. not in the examples directory). I suppose a config parameter could be added to specify the backend that the config is intended for (and write it when reading the config), then ask the user if this does not match the real backend without breaking every existing config.

As i currently don't have a lot of time to spend on this project, i'm not going to implement this for now, but would merge a pull request if it keeps backwards compatibility with existing configs.

dokutan avatar Jan 31 '24 22:01 dokutan

Understood, I haven't coded c++ in like 20 years so... :)

Want me to leave it open or close it?

BloodBlight avatar Jan 31 '24 22:01 BloodBlight

Feel free to leave it open, i might implement this when i have more time, or someone else gives it a try.

dokutan avatar Jan 31 '24 22:01 dokutan