Fix list out of range when prime_length is set to 0 (no priming)#15
Open
attahiruj wants to merge 1 commit into
Open
Fix list out of range when prime_length is set to 0 (no priming)#15attahiruj wants to merge 1 commit into
attahiruj wants to merge 1 commit into
Conversation
attahiruj
force-pushed
the
no_prime_fix
branch
from
80dd033 to
c4ec395
Compare
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.
G-code path generation breaks when prime_length is set to 0 (don't need priming in the G-code generated).
The simple fix was to skip any empty path in _paths_gcode.