AD: Getting rid of nodes in curves

[DarkClown]

I generated an object consisting of  a couple of paths. Converted these seperate objects into one curve - but I'm struggling now how to get rid of the nodes to really get one single object (as you would using the compound command). Any ideas?

[thomaso]

1. Move Tool: Select all –> menu Layer > Geometry > Merge Curves

2. Node Tool: Context Toolbar -> Smooth Curve*
(* this function seems to work as expected with straight, not curvy lines only)

[DarkClown]

Thanks, Thomaso, looks exactly what I need ....
Unfortunately, it does not work in my case: (yes, I did "merge curves" before and had one single curve to merge)

[thomaso]

Exactly the same strange curvy result by "Smooth Curve" to me with such lines. So "Smooth Curve" may even fail with purely sharp nodes + just straight lines. In that case I don't see an alternative to get rid of unwanted nodes than manually deleting them. It's indeed a pity that Serif never fixed or properly coded the buggy "Smooth Curve" function.

[DarkClown]

jup, that's the problem .... maybe someone from serif can comment on that? ( @Dan C @Patrick Connor)

[R C-R]

On 7/24/2024 at 7:08 AM, DarkClown said:

... but I'm struggling now how to get rid of the nodes to really get one single object ...

As a side note, remember that a Curves layer contains more than one curve object (even though at times the Layers panel temporarily may not update to remove the "s" if you delete all but one of its curve objects).

But that aside, the Smooth Curve function has never worked very well so what I almost always end up doing is manually selecting & deleting the nodes the design does not need and/or sharpening any curved ones I don't want curved.

[NathanC]

We have some historical reports logged of user files encountering paths 'collapsing' when using the smooth curves function as well as a more specific report on curve sections being removed entirely. I've created a quick sample file comprised of straight paths I am also observing these same failures shown in the recording and screenshot. The function does certainly have room for much improvement so i'll log this with the developers.

Ideally a 'Simplify Path' function similar to illustrators would be beneficial in this scenario so hopefully it will be considered in a future version as it is a popular request.

[thomaso]

1 hour ago, NathanC said:

The function does certainly have room for much improvement so i'll log this with the developers.

@NathanC, Doesn't this problem also concern the Help for line & shape editing ? Almost each of the six "Action" buttons of the Context Toolbar is described there... just the function "Smooth Curve" is not listed. – So it maybe unclear to the users what this feature actually is supposed to do according to the developer's code or ideas.
– Can the missing text get added to Help? (regardless of a future tool improvement / a later 'Simplify Path' function)

Also the Serif video tutorial on creating vector curves doesn't shed more light on this but mentions only “Break Curve” among the “Actions” of the ContextToolbar:
https://youtu.be/c2id9uYJ1-A?si=VJe222wDN65bEh4D&t=222

[NathanC]

34 minutes ago, thomaso said:

oesn't this problem also concern the Help for line & shape editing ? Almost each of the six "Action" buttons of the Context Toolbar is described there... just the function "Smooth Curve" is not listed. – So it maybe unclear to the users what this feature actually is supposed to do according to the developer's code or ideas.
– Can the missing text get added to Help? (regardless of a future tool improvement / a later 'Simplify Path' function)

It's covered in the 'Node tool' article but is missing from the 'Edit Curves and Shapes' article you've linked, i'll raise this with the docs team.

35 minutes ago, thomaso said:

Also the Serif video tutorial on creating vector curves doesn't shed more light on this but mentions only “Break Curve” among the “Actions” of the ContextToolbar:
https://youtu.be/c2id9uYJ1-A?si=VJe222wDN65bEh4D&t=222

I'll pass this feedback along to the team, but I don't think this can be retrospectively corrected in the existing video tutorial.