Solve #78 issue, correct order axis movement defined en queued option#79
Open
xmon wants to merge 1 commit intokirkas:masterfrom
Open
Solve #78 issue, correct order axis movement defined en queued option#79xmon wants to merge 1 commit intokirkas:masterfrom
xmon wants to merge 1 commit intokirkas:masterfrom
Conversation
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.
Sorry I'm not familiar with using grunt.js. That is why I have not been able to follow your request.
There is a fault when the "queued" option is set, since regardless of whether it is set to "x" or "y", the first movement that is always performed is on the Y axis.
This pull request solves this problem.