Skip to content

stroke() function with dashed stroke returns first piece last #528

@Keavon

Description

@Keavon

Graphite wraps Kurbo's stroke() with our Solidify Stroke node. I am noticing that, when a dashed line (regardless of cap style) is involved, it returns the first piece in the wrong order, at the very end. See this demonstration where we move an object along the edges of each subpath in order, starting from the second piece, going to the last piece, then returning to end with the first piece:

capture_14_.mp4

I had stroke() print out its SVG directly, and I split up each M command into its own <path /> so I can delete each one sequentially to show the ordering issue, directly from Kurbo (not a Graphite node bug):

capture_15_.mp4

We can also see that this causes problems assigning colors along a gradient to each separate subpath:

Image

If we add in a more subpaths as part of the input compound path, we see it affects every individual subpath:

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions