Refactor vertex functions for composite paths #6606
Closed
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.
Addresses #6560
This PR introduces the suggested way (as discussed in #6560 by @davepagurek and @GregStanton ) to refactor endShape to enable it for composite paths for 2D.
Changes:
Vertex
,BezierVertex
,QuadraticVertex
,CurveVertex
)endShape
by looping through the vertex objects.Shape
,Contour
,ContourSegment
to organize the construction and manipulation of the vertex objects.Screenshots of the change:
All the vertex objects works as expected!
PR Checklist
npm run lint
passes