Documentation Archive Developer
Search

ADC Home > Reference Library > Technical Q&As > Legacy Documents > Printing >

Legacy Documentclose button

Important: This document is part of the Legacy section of the ADC Reference Library. This information should not be used for new development.

Current information on this Reference Library topic can be found here:

Moving Code in DespoolPage to GXSetUpPageImageData

Important for all Apple Printing and Graphics Developers:

The information in this Technical Q & A is still relevant up to and including Mac OS 7.6 with QuickDraw GX 1.1.5. Beginning with the release of Mac OS 8.0, however, Apple plans to deliver a system which incorporates QuickDraw GX graphics and typography only. QuickDraw GX printer drivers and GX printing extensions will not be supported in Mac OS 8.0 or in future Mac OS releases. Apple's goal is to simplify the user experience of printing by unifying the Macintosh graphic and printing architectures and standardizing on the classic Printing Manager.

For details on Apple's official announcement, refer to </dev/technotes/gxchange.html>

Q: After reading the information on GXSetupPageImageData, I began to wonder whether some code I currently have in DespoolPage needs to be moved over to this message. My code handles horizontal and vertical flipping, if needed. I presume that this is the sort of thing that should be moved, but I wanted to check this out first. What happens in the following example?

A user wants to print a 2-page document on one sheet of paper using the N-Up extension. The two logical pages have different sets of flipping options, because each page has its own custom format. Presumably, these two logical pages are merged into one physical page using GXSetupPageImageData. Which set of flipping options is used (or am I confused about when logical pages are turned into one physical page)?

A: You're correct. You should move the code you have in DespoolPage to GXSetupPageImageData. Regarding your example, it sounds as though you're confusing logical pages, because the extension would break your print job into two pages.

[May 01 1995]