<html>
<body>
Some time ago, you were kind enough to suggest a work-around for
the following behaviour:
<dl>
<dd>inside of pscustom \psbezier takes only three arguments when it
<dd>follows another curve. The end of the preceding line is always
<dd>the starting point for the next one.
</dl>The suggested work-around is<br>
<br>
<pre>\makeatletter
\def\<a href="http://tug.org/mailman/listinfo/pstricks">psbezier at
ii</a>{%
\<a href="http://tug.org/mailman/listinfo/pstricks">addto at
pscode</a>{%
%\<a href="http://tug.org/mailman/listinfo/pstricks">pst at cp
</a> \ifshowpoints true \else false \fi
\<a href="http://tug.org/mailman/listinfo/pstricks">tx
at OpenBezier
</a> \ifshowpoints
\<a href="http://tug.org/mailman/listinfo/pstricks">tx at
BezierShowPoints</a> \fi}%
\<a href="http://tug.org/mailman/listinfo/pstricks">end at
OpenObj</a>}
\makeatother
</pre> <br>
However, it appears that this does not fix recent PSTricks package
versions.<br>
I’ve updated my MikTeX 2.7 to the most recent version to confirm.<br>
<br>
This behavior would seem to be a bug. The coordinate data defining a
spline<br>
depend on whether the path will be embedded in a \pscustom
environment,<br>
which may not be known when the coordinates are generated, and the
first<br>
segment may not be known.<br>
<br>
The following example illustrates the problem:<br>
<br>
\psset{unit=1in,cornersize=absolute,dimen=middle}%<br>
\begin{pspicture}(0,0)(0.75,0.5)%<br>
\pscustom[fillstyle=solid, linecolor=black, fillcolor=lightgray]{<br>
\psline(0,0)(0,0.5)(0,0.5)(0.5,0.5)<br>
\psbezier(0.5,0.5)(0.625,0.5)(0.75,0.375)(0.75,0.25)<br>
\psline(0.75,0.25)(0.75,0)(0.75,0)(0,0)<br>
}%<br>
\end{pspicture}%<br>
<br>
<x-sigsep><p></x-sigsep>
Dwight Aplevich</body>
</html>