Comment 63 for bug 165865

Fixed in new patch. Those options would be very welcome.

New observations:

1) Create path
2) Assign marker (I did a mid)
3) Change stroke color

Result is that the marker color is not changed. Two things about this: I would think a lot of people would prefer the marker color be updated in sync when changing the stroke color if possible. I will be honest, I like the marker color not being locked to the stroke color yet relatively easy to change. Maybe an option to "Update colors on object color change" enabled by default? (unless this is actually not intended and a bug)

Now:

4) Change that marker to a different one
5) Change marker back to first one assigned from the custom list

Result is that it forks the existing first custom marker with the new color rather than actually using that marker as-is (and as displayed in the custom section)... I could see your second proposed option fixing that and to me it seems like not changing custom markers by default would be preferable.

Issue 1: There is an actual problem though if you toggle between markers in the custom section it continues (forking) even if the color has not changed which leads to a lot of unnecessary duplicates.

Issue 2: I also noticed that if I toggle between the custom markers enough and it keeps creating dupes it eventually gives them different names (not a complaint, just seemed odd that initial ones retained name for multiple dupes before starting the unique names). Perhaps it should just give unique names from the get-go?