I'd like to avoid muddying up the simplicity of the one click stroke to path with extra options. Adding options would require a switch somewhere, or a popup dialog.

Imho, our current methods for user interaction with clones has been clunky at best. Just noticed that the bug wishlist item says that the marker strokes are also converted to fills...

However, since there is no other way (that I know of) to convert markers to clones, maybe we should include that as a separate function "Markers to Clones", and allow Stroke To Path to convert all the strokes in the object to path (including the markers), which I think is the expected behaviour in most cases where you are using Stroke to Path.

Would we like to see some more use-case analysis for scenarios involving markers in regards to different options for handling them?

Another way to handle it is that when the function Stroke to Path is complete, the markers are converted to clones, grouped, and them highlighted, so the user has the option to run the command again to convert the marker strokes to paths/fills as well.

The logic:

User wants to convert strokes to paths in a markered object (probably rare)

User runs Stroke to Path, stroke to Path does all of the following in sequence:

a. Stroke to path converts all base object strokes to paths, as per new function

b. Stroke to path them groups all objects which are not included in previous action and selects them so the user knows they have been broken off of the base object, but not converted to fills yet.

c. User them has the option to run stroke to path on the highlighted/selected objects instantly.

Thoughts?

-C

-C