Trigger and Move Button have a lot of dropouts
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 528
- Forks
- 173
- PR merge metrics
- No merged PRs in 30d
Description
All Buttons except Trigger and Move have a high fidelity. Pressing them gives the expected response of pressed and released. The Trigger and Move are less responsive. The faster you click one of those, the less click events are published. This behaviour is seen in the example and example_new_api, Windows 7 and 10 with inbuilt Bluetooth.
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 dropout in the example and example_new_api programs on Windows with built-in Bluetooth, comparing Trigger and Move against the other buttons. Trace where button press and release events are published; done means rapid Trigger and Move clicks reliably produce the expected events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100