Hi Jim, > As the author of the memory buffer version, I tried to implement the > functionality of the file buffer version. I thought so, since for the file buffer version it's also not a good solution. Al least if you work with both streams one writes in one buffer.
> That said, I think making a > copy of the buffer is the best way to go forward. The purpose of the > plcpstrm call was to copy a buffer so that it could be rendered by a > different device (for example to generate a postscript output from a > plot that is being displayed). > > The advantage to maintaining one plot buffer is to have the capability > to maintain the same plot on two different output devices > simultaneously. > Also a nice idea, what about plclstrm for clone stream? > The name plcpstrm, in my opinion, implies making a copy of the current > state and not linking the two plots. If we do want to maintain a plot > buffer that is linked to multiple device, perhaps a new API call should > be implemented. Regards, Werner ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
