feat: adds _CLIENT_LINEAR_MOVE macro support #1530
Merged
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
Signed-off-by: Pedro Lamas <[email protected]>
pedrolamas
force-pushed
the
pedrolamas/client-linear-move-macro
branch
from
941c35d
to
c40df1d
Compare
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.
This mitigates the "noise" from the toolhead and extruder movement as we currently do call
SAVE_GCODE_STATEandRESTORE_GCODE_STATEon each movement.The changes on this PR will check if a
_CLIENT_LINEAR_MOVEmacro exists, and if so, it will use that to perform every toolhead and extruder movement.This macro will be provided as a default in fluidd-config and mainsail-config, but can obviously be written by anyone.
Before
After (if macro exists)