|
From: Ethan A M. <merritt@u.washington.edu> - 2006-02-05 05:50:41
|
On Saturday 04 February 2006 07:50 pm, Mojca Miklavec wrote: > On 2/5/06, Hans-Bernhard Br=F6ker wrote: > > > > We don't need a term->polyline(). The only thing needed to complete > > the existing API in this area would be a term->closecycle() or some > > such, to distinguish between open and closed polylines. We don't need that either. I've just placed a patch for post.trm on SourceForge that simply keeps track of where the current polyline started. If that point is reached again, then the polyline is closed off with "closepath stroke" rather than "<xend> <yend> lineto stroke". Seems to work fine, but have a look and see if you can improve it further. As noted in a code comment, it seems to have the side effect of triggering a subsequent "1.000 UL". Harmless, but unnecessary. > I thought this was a valid sequence of commands > move(0,0) > vect(1,2) > put_text(3,3,"abc") > vect(0,1) It is a legal sequence of commands, although I don't think it can be generated by any existing operation in gnuplot. The second vect() command above will start a new polyline whose origin is somewhere in the string. =2D-=20 Ethan A Merritt Biomolecular Structure Center University of Washington, Seattle 98195-7742 |