rust-windowing / rust-windowing/winit
Possibility to distinguish if wheel event from Touchpad or MouseWheel
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 1.3k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 9
Description
Description
Currently when a MouseWheel event is triggered, the TouchPhase is set to Moved. For the Touchpad the phases Started, Moved and Ended are used.
It is confusing when a wheel event with a phase of Moved is send without the Start.
Qt is using NoScrollPhase for mouse wheel events and for the Touchpad start, update and end (https://doc.qt.io/qt-6/qt.html#ScrollPhase-enum)
Relevant platforms
No response
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 how MouseWheel events assign TouchPhase and where touchpad phases are represented in the event API. Compare the requested behavior with Qt's NoScrollPhase distinction, then define the event semantics and verify that mouse-wheel and touchpad sequences can be distinguished consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100