(fix) Hotcue press sets drag start pos to use correct distance threshold #14367
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
Previously, dnd was initiated instantly and hotkeys could not be applied then
|
Ups, draft state was not intentional, this is ready for merge. |
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.
Previously, drag'n'drop could be initiated unintentionally very easily because
DragAndDropHelperdidn't have the correct drag start point, ie. starts a drag for even the shortest cursor move and thereby prohibits use of hotkeys(behaviour may depend on desktop environment).
The result is that hotkeys could not be applied during unintentinal DnD.
Fixes #14365