Subject: Re: Bug in PostScript arrows [ was Re: Updated HTML version of demo scripts now on SourceForge

[Petr M. <mi...@ph...>]

> > I don't see any dashes, but yes - Arrow styles 1,3,4, and 5 in the demo
> > produce arrowheads only, with no shaft.
> >
> > I wonder when this broke, and what broke it?
>
> Found it.
> It was broken by a patch from Mar 2003 that removed PS_FLUSH_PATH
> from the start of PS_filled_polygon(). ChangeLog says:
>
> 2003-03-22  Petr Mikulik  <mi...@ph...>
>         * term/post.trm(PS_filled_polygon): Don't call PS_FLUSH_PATH but reset
>         ps_path_count instead (flush is automatic). Fixes broken pm3d map
>         layout (required by pm3dConvert*.awk scripts) due to "stroke\n" in
>         PS_FLUSH_PATH.
>
> Restoring the PS_FLUSH_PATH in post.trm would fix the current problem.
>
> Petr:
>
>     Can you re-examine the problem with the awk scripts?  Because it
> seems that the flush is in fact needed here.   It is not correct that the
> flush of the previous element is automatic.  Without an explicit "stroke"
> command, any line followed immediately by a filled polygon is never drawn.

As I remember, my patch fixed broken filled objects -- pm3d and
filledcurves. This gnuplot-automatic "stroke" made the stroke before
"closepath" or "fillpath" operators thus coloring only parts of (some?
large?) filled objects. "stroke" can be used after "{close|fill}path"
(but it is not necessary I think).

As a test, try "set pm3d map; splot x" (or "splot y") (maybe adjust
sampling) with output to a color postscript file, pass it through
pm3dConvert....awk script and see whether it is OK in ghostview.

Also with some of "plot ... with filledcurves".

---
Petr Mikulik