Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
8

Stroke is broken for multiple subpaths per shape layer

Participant ,
Oct 02, 2023 Oct 02, 2023

Robert29264429yt0q_0-1696276174625.png

Red is an example of multiple open-ended subpaths in a single shape layer.
Green is an example of a single open-ended subpath in a single shape layer.

As you can see: multiple sub-paths completely break dashing.

This may be related to another issue:

Robert29264429yt0q_1-1696276327719.png

Upper version is a single open-ended sub-path on a single shape layer
Lower version are two open-ended sub-paths on a single shape layer. The shapes seems to act as though it were closed, however: it's not actually closed. There are no edges linking the end vertices of that path, and likewise, the triangle is constructed of 3 verts and 2 edges - the bottom-right edge shouldn't exist.

Bug Unresolved
TOPICS
Windows
463
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
7 Comments
Community Expert ,
Oct 02, 2023 Oct 02, 2023

Confirming that is reproducible here on V25.0 and Windows 11

Dave

Translate
Report
Participant ,
Oct 03, 2023 Oct 03, 2023

A clearer illustration of the self-closing symptom when multiple subpaths exist on a shape layer:

 

ThatRobHuman_0-1696391703036.png

 

Note that the red is the actual path, and the blue is the stroke that results.

 

 

This is really hampering my workflow.

Translate
Report
Community Expert ,
Oct 03, 2023 Oct 03, 2023

Problem is not visible with only one path or subpath on my side, it appears when second subpath is drawn on existing shape layer.

Translate
Report
Participant ,
Oct 03, 2023 Oct 03, 2023

Correct. That's what I meant by "multiple subpaths per shape layer"

Translate
Report
Participant ,
Oct 31, 2023 Oct 31, 2023

still an issue in 25.1

Translate
Report
Participant ,
Jan 03, 2024 Jan 03, 2024

Still an issue in 25.3.1

Translate
Report
Participant ,
Jun 05, 2024 Jun 05, 2024
LATEST

still an issue in 25.9

Translate
Report