EmptyTriangle marker get filled if its colour is matched to the stroke

Bug #1201045 reported by Atcold
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Confirmed
Low
Unassigned

Bug Description

EmptyTriangle marker gets filled with the stroke colour when the Match Stroke extension is used.

Steps:
1. Drow an EmptyTriangle arrow
2. Change the stroke colour
3. Extension -> Modify Path -> Color Markers to Match Stroke

An SVG is attached.

Revision history for this message
Atcold (atcold) wrote :
Revision history for this message
Alvin Penner (apenner) wrote :

- confirmed on Windows XP, Inkscape rev 12417

the original marker, #EmptyTriangleOutL, has the style property:
fill:#ffffff;fill-rule:evenodd;stroke:#000000;stroke-width:1pt;marker-start:none
in which the stroke is black and the fill is white.

after using the extension, the new marker has the style property:
stroke-opacity:1;fill-rule:evenodd;marker-start:none;fill-opacity:1;stroke:#008000;stroke-width:1pt;fill:#008000
in which both the fill and stroke are green. In the case of a white fill color, it would probably be best to leave the fill color unchanged.

Changed in inkscape:
status: New → Confirmed
Revision history for this message
su_v (suv-lp) wrote :

Alvin Penner wrote:
> - confirmed on Windows XP, Inkscape rev 12417

Please note that while the reporter does not reveal OS/platform and Inkscape version, the SVG file the reporter provided was generated with

> inkscape:version="0.48.2 r9819"

Both internal handling of marker colors as well as the python extension to match the color of markers to the stroke has significantly changed in current trunk compared to the rather dated release of 0.48.2.

Related report for stable 0.48.x:
Bug #692582 Color markers to match stroke extension does not copy the fill mode

Related report for regression in trunk:
Bug #1055796 Markers customized colors not persistant

tags: added: extensions-plugins markers
Revision history for this message
Alvin Penner (apenner) wrote :

thanks, ~suv, for the references. I see this has a long and rich history, so I hope I am not re-kindling a fire here. But I think this is indeed a duplicate of the Bug 692582. And I think that the original bug report has not actually been fixed.
    It appears that currently the original line stroke color is being copied onto both the stroke and the fill color of the marker. In the case of the "Empty" markers this is not desirable. The stock markers appear to come in two styles, those that have a white fill (called Empty) and those that have a black fill. I would suggest that, if the marker has a white fill, then it should be kept as white, and only the marker stroke color should be modified.

Revision history for this message
Atcold (atcold) wrote :

Yes, I apologise for the missing information (it's my first bug report ^^).

Platforms: Mac OS X v.10.7.5, Inkscape: 0.48.2 r9819
Platform: Ubuntu 13.04, Inkscape: 0.48.4 r9939

If I can add my personal opinion, it would be so terribly easy to just add a `Colour marker` section on the `Stroke paint` palette containing the two options `Stroke colour` and `Fill colour` which would point to the `stroke` and `fill` fields of all markers for a given path in the XML code. This is because if I am drawing arrows on a coloured background, say on top of another shape, I would like to give the impression that the markers are transparent and not "white". Or, alternatively, provide just a checkbox where someone could specify whether to copy the stroke info to the marker (which should be `on` by default) and an RGBA hexadecimal field for the `Marker fill` field. Actually, I like this second solution even more! ^^

Anyway, now that I have found out I can edit the XML by myself, my thesis is safe! :)
Thank you guys for this awesome piece of SW!

su_v (suv-lp)
Changed in inkscape:
importance: Undecided → Low
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.