Hi Michael,
> Just to add a single comment from a PyX user: The hatch filling was
> essentially the only feature that caused problems when printing, as
> far as I experienced. The printer was a high-class Lexmark with
> sufficient memory, but the way the hatched patterns are created in PyX
> made it stumble.
As we know, also Ghostscript is not a particularly perfect hatch
interpreter ;-)
> Instead of adding more features to this type of patterns, I would
> rather suggest to remove the feature or replace it by a more stable
> one (hatching "by hand": stroking many lines and then clip). In
> combination with parallel deformers, this can be used to create an
> effect such as patterning a line.
So basically we would take the bounding box of the object to determine
the size of the underlying "lattice" and then do it ourselves. But
what kind of object in the PyX class hierarchy would this then be?
Jörg
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
PyX-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyx-user
