rust-windowing / rust-windowing/winit
Dual-function (tap for X, hold for Y) keys do not reliably report the tapped key as pressed
Open
Nobody has claimed this yet.
B - bug
DS - win32
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 1.3k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 9
Description
Description
For dual-function keys (tap for X, hold for Y) on my mechanical keyboard (Moonlander) the tap key is only rarely (estimate 1 in 20) detected by Bevy's input system. I have a regular keyboard attached for which the keypresses work 100% of the time.
Windows version
Edition Windows 11 Home
Version 24H2
Installed on 2025-09-18
OS build 26100.7171
Experience Windows Feature Experience Pack 1000.26100.265.0
Winit version
0.30.12
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 reproducing the issue with winit 0.30.12 on Windows 11 using the Moonlander dual-function keys, then compare its input reports with a regular keyboard. The issue names no source file or test; done means tap actions are reliably reported as pressed rather than only about 1 in 20 times.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100