I can still report it to EFI (maker of Fiery RIPs), and probably
will, but I
think that might be barking up the wrong tree as it does seem
something
specific to Print Window (which just happens to be REALbasic-based).
I should probably say that the print jobs Print Window sends are all
Vector-based, using StringShapes, Group2Ds, etc. Maybe something
specific
to those classes?
Maybe. I'd start by creating a "debug" version of PrintWindow that
doesn't use particular classes when printing; for example, compile it
and comment out all the lines that call for StringShapes. Eventually,
you'll hit on which one is causing the RIP to crash.
This is the normal first-step troubleshooting process for Quark/
InDesign/Illustrator/WhatHaveYou documents that won't print for
unknown reasons: eliminate each page item until it prints. Tedious,
but extremely effective.
Eric Williams
Oxalyn Software
http://software.oxalyn.com/
AE Monitor
http://software.oxalyn.com/AEMonitor/
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
