Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!apple!keith
From: keith@Apple.COM (Keith Rollin)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Printing Example Code
Keywords: mac printing is a pain in the petute
Message-ID: <28876@apple.Apple.COM>
Date: 13 Apr 89 03:30:26 GMT
References: <451@biar.UUCP>
Organization: Apple Computer Inc, Cupertino, CA
Lines: 32

In article <451@biar.UUCP> trebor@biar.UUCP (Robert J Woodhead) writes:
>
>Well, I'm sick of screwing around with the printer drivers.  And since
>
>This is to say, code that:
>
>	* Prints on all Apple supported printers
>	* Prints in all selectable resolution modes
>	* Lets the user abort
>	* Prints under Finder & Multifinder on ALL machines
>	* is in the form of "it's all set up, insert your code to
>	  image into this bitmap here".
>

One thing that satisfies all of these conditions is the TStdPrintHandler that
comes with MacApp. With MacApp, you don't even have to THINK about printing;
it comes virtually automatically. If you just want to print out exactly what
you see on the screen, then all you have to do is add four lines of source
code to your program. Automagically, the print items in your file menu (Page
setup, Print One, and Print...) are enabled and work. The user can abort at
any time, and you don't even have to supply the items you mentioned in bullet
#5, as your main drawing code is autumatically re-used.

If your printing needs are little more extravagent, MacApp can accomodate that
as well.

------------------------------------------------------------------------------
Keith Rollin  ---  Apple Computer, Inc.  ---  Developer Technical Support
INTERNET: keith@apple.com
    UUCP: {decwrl, hoptoad, nsc, sun, amdahl}!apple!keith
"Argue for your Apple, and sure enough, it's yours" - Keith Rollin, Contusions