add functions to check which button triggered a drag start & end #2507
Conversation
This file contains 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
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.
currently its hard to figure out which button triggered a drag start & end event:
drag_started, checkingresponse.drag_started() && ui.input().pointer.button_down( ... )usually works. however this could be false positive when multiple buttons are dragging at the same time.drag_released, there seems to be no way at all.to improve this,
button_pressedis added to precisely check buttons of drag starts. and makebutton_releasedindependent of clicks (closes #2094) to check buttons of drag releases.some utility functions are added to
Responsefor convenience.