🚀 go-pugleaf

In article <2246@husc6.harvard.edu> siegel@endor.UUCP (Rich Siegel) writes:
>In article <16701@well.sf.ca.us> svc@well.UUCP (Leonard Rosenthol) writes:
>>In article <1990Mar14.041825.18302@Neon.Stanford.EDU> kaufman@Neon.Stanford.EDU (Marc T. Kaufman) writes:
>
>> [my original comments removed for inews]
>
>	So why not spool to a local disk file, and then image the text from
>that file using the high-level calls? There's no need to pose a dialog;
>just use the default print settings. 
>
	That will only solve the problem for some users.  As I point out in
my original comments, which you chose to leave out of your quote, there are
_A NUMBER_ of instances where the data _MUST_ arrive as it is xmitted and if
I have to wait for a whole page to be captured (and then imaged) that is most
certianly not _IMMEDIATE_.  Also, there are situations where you may not get
a 'close printer' sequence...
	Other issues such as do you print every page as the page is complete?
or do you wait for all the data and then print the whole document?  
	Spooling is a nice concept for a lot of things, and we will probably
investigate it for future products - _BUT_ it does not solve the problem that
Apple is dedicated to connectivity and telecommuncations and yet they refused
to be concerned about this aspect of it.  Great, I can talk to my Vax, but I
can not print.....

>
>~~~~~~~~~~~~~~~
> Rich Siegel
> Staff Software Developer
> Symantec Corporation, Language Products Group
>
	Speaking of which, all of the Symantec Language Products use the low
level printer calls when doing nonToolbox printing for standard Pascal and C
I/O routines...eh Rich?? ;-)



-- 
+--------------------------------------------------+
Leonard Rosenthol        |  GEnie : MACgician
Lazerware, inc.          |  MacNet: MACgician
UUCP: svc@well.UUCP      |  ALink : D0025