It looks like you know more about this than I do, now.
I have more or less clear how to fix that (not a usb guru!) but I have
make some api changes, and this part I wanted to hear your opinion.
Why does HIDReportItem expose a UsageMinimum and UsageMaximum? Despite
not making sense anymore, wouldn't these properties fit better on
HIDCollection? An item is expected to have just its Usage ID. Perhaps I
My proposal is to get rid of these methods on Items and move elsewhere
(collection?). As no longer would be a single min/max pair, this should
expressed as an usage array or range array.
It looks like you know more about this than I do, now. In that ticket we
have confirmed that the existing code is incorrect and does not handle this
case. Do the changes you think are needed, and we'll try to test it on
various usb-hid devices and see how it does. That's the best way to be sure
we're doing the right thing :)
Adrien / PulkoMandy