Shift release generating wrong code when both Shifts are held down
Open
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 68
- Forks
- 82
- PR merge metrics
- No merged PRs in 30d
Description
When both Shift keys are held down, releasing one produces a key-event% for which get-key-code produces 'shift or 'rshift, not 'release. This is causing client code (e.g. 2htdp/universe) to misidentify the release as a keypress.
Contributor guide
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 tracing the key-event% and get-key-code behavior described in the issue, then check how 2htdp/universe consumes the resulting event. Reproduce the case where both Shift keys are held and one is released; done means that release is identified as 'release rather than 'shift or 'rshift.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100