Should probably use native windows APIs on Windows

[tksuoran]

One Windows, it would probably make sense to use Windows raw input and HidP APIs

Useful headers:

• hidsdi.h
• hidusage.h
• hidpi.h

Useful functions:

• RegisterRawInputDevices()
• GetRawInputDeviceInfo()
• HidP_GetLinkCollectionNodes()
• HidP_GetUsages()
• HidP_GetScaledUsageValue()
• HidP_GetButtonCaps()
• HidP_GetValueCaps()

Using these APIs, there is no need to rely on any information about devices hard coded into the "driver" code. Everything needed can be queried using HidP API.

[ruevs]

In fact I seriously considered doing that! I read your (presumably) comment on the forum https://forum.3dconnexion.com/viewtopic.php?p=117278#p117278 back when you wrote it in 2023. At the time you mentioned "improving [your] own space mouse support" - is it open source?

Eventually I decided not to interrogate, parse and handle the HID device in a "generic" way. It is fairly easy to do on Windows, Linux, WebHID (and presumably macOS) but on bare metal (an embedded device) where the USB host support layer may be very "thin" it may be rather cumbersome.