[Xcircuit-dev] hidden files in xcircuit-3.6.73-1

Wim Vereecken wim.vereecken at esat.kuleuven.be
Tue Jan 2 07:59:58 PST 2007


On Saturday 30 December 2006 02:49, R. Timothy Edwards wrote:
> Dear Wim,
>
> I would like to point out one problem that may need to be addressed
> (I haven't yet looked at the Perl code in detail).  Matlab will write
> array data as generated, which may contain thousands of points.
> XCircuit will handle this with no problem, since it just allocates
> memory as necessary for any element.  Ghostscript, likewise, should
> have no problem with it.  Specific PostScript printers, though, (and
> this is according to the PostScript manual) may have a limited stack
> depth and may generate an error if a polygon is too large.  I haven't
> ever encountered this limit on a printer, and would be interested to
> know if anyone has.  Maybe all printer implementations of PostScript
> are designed to handle arbitrarily deep data stacks.

Dear Tim,

I indeed encountered the problem of a limited stack depth (in ghostview) when 
I first tried to encapsulate a large matlab plot in an XCircuit library 
object. In postscript this would be pushed completely on the stack. The 
Matlab eps-export routine however seems to split large polygons into several 
smaller parts. The current conversion script just translates between the 
matlab-eps and the xcircuit-eps format: if a large polygon is selected, you 
will notice that it consists out of several smaller parts... When several of 
these parts are joined in an object, in my experience this will result in a 
stack overflow in ghostview.

> Can I make a link to it from the XCircuit web page?
Of course you are free to link (or copy) this Perl script to the XCircuit home 
page...

Kind regards,
Wim

--
Wim Vereecken
Research assistant
K.U.Leuven, Dept. ESAT-MICAS
Kasteelpark Arenberg 10
B-3001 Leuven
Belgium
Tel. +32 16 321070
FAX  +32 16 321975

Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm




More information about the Xcircuit-dev mailing list