Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!rutgers!apple!vsi1!frame!glc
From: glc@frame.UUCP (Greg Cockroft)
Newsgroups: comp.sys.next
Subject: Re: Various comments/questions/suggestions
Message-ID: <3539@frame.UUCP>
Date: 15 May 89 05:48:15 GMT
Reply-To: glc@frame.com (Greg Cockroft)
Distribution: usa
Organization: Frame Technology Corp. San Jose, Calif.
Lines: 28
Disclaimer: Author Is Responsibility For Contents


>>PRINTING (from applications):
>>Many 'beta' applications fry PS when you try to print (FrameMake, sometimes
>>WriteNow).
>
>Well, FrameMaker doesn't appear to print through lpd, so it's *got* to
>be doing something wrong. (print from Frame with not enough paper;
>you'll never see an "out-of-paper" dialog box, and lpd will think all
>is well)
>
>  But I've never had a problem with the window system getting
>scrogged, just the printer.  What exactly happens to you?

FrameMaker prints by sub-classing the view class versus spooling
a PostScript file and forking off an lpr.

Which means npd is used instead of lpd.

This is the recommended way of printing.

The only fatal bug in printing reported occurrs if you leave
object handles displayed while printing.

I have a fix for this but I'm going to wait and post it when I
have patterns printing.


	-greg.