Conversation
2 tasks
Murmele
force-pushed
the
mm/move_history
branch
from
September 25, 2026 08:52
54d7cdb to
281374d
Compare
#Conflicts: # winit-core/src/event.rs # winit-core/src/event_loop/mod.rs # winit-wayland/src/seat/touch/mod.rs
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
changelogmodule if knowledge of this change could be valuable to usersAndroid and Ios do not publish touch events for every single touch movement, but collect them and publish them lower frequent. Using only the lower frequent events, velocity estimation is not appropriate (For a 50ms gesture we would get with 60Hz only 3 events).
Android and Apple expose additional touch event history which can be used.
Implemented for:
@kchibisov We could further discuss if we wanna collect all events and send it out whenever the frame event occured? https://wayland-book.com/seat/touch.html (Clients should accumulate all wl_touch events as they're received, then process pending inputs as a single touch event when the "frame" event is received.)