On Fri, Jul 11, 2008 at 8:00 PM, Philip Dow <[EMAIL PROTECTED]> wrote:
> > That's right, I realized after posting the message that I should have > boiled it down to the following: > > + (NSPrintOperation *)PDFOperationWithView:insideRect:toData:printInfo: > This operation produces a single page of PDF no matter what print settings > I pass in, one very long page. > > + (NSPrintOperation *)printOperationWithView:printInfo:aPrintInfo > This operation when set to write the data to disk correctly produces a > paginated document. > > It's like the NSPrintOperation methods do not allow you to create a > multi-page PDF in memory. You have to write it to disk first. > > I did take a look at the output in both operations, and that's exactly what > happens. The fist op gives you one long page of pdf, which is unreadable > when scaled to fit inside the quicklook preview. The second op gives you > what you expect. > > I suppose I could use the second operation and then read back in the > correctly paginated pdf, but then I'm writing out to the hard disk any time > the user wants to quicklook my document. This seems like a terrible waste of > resources. > Please, don't do that as your plug-in really should avoid doing anything but reading stuff on disk. Maybe someone from the AppKit team will be able to find the source of your problem. -- Julien > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
