Conversation
Contributor
Author
|
Is there anything I can do to move this forward? |
Member
|
@trobrock sorry it slipped through the cracks of my radar, could you please rebase on master? I'd like to run tests again? |
…held before dragging
Contributor
Author
|
@route no worries. Just rebased. |
Member
|
Thanks! |
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
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.
I'm using SortableJS, which supports the ability to require the mouse be held for a period of time (in our case 300ms) before the user can drag the element.
Inspired by @swanson's work on #182 this adds the ability to add a delay between the mouse press and the drag.
This patch got our code off our custom drag_to method and onto this libraries. Usage is like this: