Add Z coordinate for GCodePath points #18
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
wawanbreton
commented
Sep 27, 2024
There was a problem hiding this comment.
@jellespijker or @rburema dont't these changes require that we make a v1 of the protocol ?
Version 0 is 'special' in the sense that all versions before 1.0.0 are considered 'in development'. See: https://semver.org/#how-should-i-deal-with-revisions-in-the-0yz-initial-development-phase This is specifically why I've requested that we stay in version 0 for a long time, so when we finally do have a 1.0, it'll be stable enough to not need major changes every year. |
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.
GCodePath now contain a Z coordinate because each individual point may have a vertical offset
CURA-12080
CURA-12081