Internal perimeters first on overhangs #11418
Open
+63
−7
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
vovodroid
force-pushed
the
first-internal-overhangs-pr
branch
from
d23c5e0 to
99cf37e
Compare
vovodroid
force-pushed
the
first-internal-overhangs-pr
branch
from
99cf37e to
df3c194
Compare
vovodroid
force-pushed
the
first-internal-overhangs-pr
branch
from
df3c194 to
284fd24
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.
Now there is option "External perimeters first", that is good for precise dimensions, but bad for overhangs. This PR adds option for automatic perimeters order for layers with overhangs present.
When both option enabled external perimeters are printed first, but not for layers with overhangs:
Without overhangs:
With overhangs:
Current limitation: this algorithm is applied for the whole layer, not just for region with overhangs: