-
Notifications
You must be signed in to change notification settings - Fork 570
fix: Backwards compatible behaviour of swipe and scroll in action_helpers #744
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
b5f05d8
Backwards compatible behaviour of swipe and scroll in action_helpers
jatalahd e09b50d
Backwards compatible behaviour of swipe and scroll in action_helpers
jatalahd 1e005ca
Backwards compatible behaviour of swipe and scroll in action_helpers
jatalahd 284d386
Backwards compatible behaviour of swipe and scroll in action_helpers
jatalahd 88b2ce3
Backwards compatible behaviour of swipe and scroll in action_helpers
jatalahd File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand the logic here - do we just reassign
actions.w3c_actionsproperty? what is then the point of having previous calls?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Previous actions are in
touch_input, so this one just updatesduration.actions.w3c_actions.pointer_action._duration = durationcan be the alternative of theActionBuilder(self, mouse=touch_input, duration=duration)to append actions intouch_inputwith the duration.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think you can also call the
create_xxxmethods on touch_input itself, liketouch_input.create_pointer_move(), right?