rust-windowing / rust-windowing/winit
How to handle MouseWheel when both pixel and line deltas are available ?
Open
Nobody has claimed this yet.
C - needs discussion
D - easy
P - low
S - api
S - enhancement
- Dominant language
- Rust
- Stars
- 6.2k
- Forks
- 1.3k
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 9
Description
In some cases (if the compositor supports it), the wayland backend can have access to both LineDelta and PixelDelta values for a given scroll event.
In this case, what should be done ?
- generate only the
PixelDeltaevent ? - generate only the
LineDeltaevent ? - generate both ?
- modify the
MouseWheelevent so that it may provide both values ?
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 Wayland backend's MouseWheel handling and the meanings of LineDelta and PixelDelta in the issue. Resolve which behavior should apply when both values are available, then define the resulting event semantics and verify the behavior for scroll events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100