microsoft / microsoft/ArduinoHidForWindows
Windows imposes limitations on HID report descriptor
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 159
- Forks
- 11
- Avg merge
- 3h 20m
- Merged PRs (30d)
- 1
Description
Admittedly this issue doesn't strictly belong here, but I also have no better place to report it. I was testing different ways to reduce the report sizes, and found that the Windows 11 host will not activate Dynamic Lighting (nor will indicate any error in Device Manager or wherever), if one of the following is true:
- The lamp count or lamp ID is placed in a single byte in the reports.
- The lamp purposes is placed in a single byte.
- The lamp kind is placed in a single byte.
The latter two are only annoyances, but the lamp ID limitation is more severe in the case of LampMultiUpdateReports, as in this report there are a series of lamp ID fields, which waste a lot of buffer space if the device wants to support updating a large number of LEDs in one report.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the report variations on a Windows 11 host, testing single-byte lamp count or ID, purpose, and kind fields. Compare whether Dynamic Lighting activates and pay particular attention to LampMultiUpdateReports; done means clearly documenting the reproducible limitation and its impact on report buffer space.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100