I have a filed a report, Bug ID# 6072333.
~Phil
On Jul 11, 2008, at 1:02 PM, Julien Jalon wrote:
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:
+
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.
+
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
If I understand correctly your point, it seems that in the first case, you
use the direct to data print operation and in the second case, you use the
direct to file print operation then read back the file in memory and send it
to Quick Look. Both methods use
Le 9 juil. 08 à 23:54, Julien Jalon a écrit :
If I understand correctly your point, it seems that in the first
case, you
use the direct to data print operation and in the second case, you
use the
direct to file print operation then read back the file in memory and
send it
to Quick Look.
Le 10 juil. 08 à 00:20, Jean-Daniel Dupas a écrit :
Le 9 juil. 08 à 23:54, Julien Jalon a écrit :
If I understand correctly your point, it seems that in the first
case, you
use the direct to data print operation and in the second case, you
use the
direct to file print operation then read
Hi all,
I am trying to generate multipage pdf data for display in a quick look
preview from rich text attributed string data. Attributed strings
don't know anything about pages, so it seems to me that I'll have to
go through the OS printing architecture to generate the multipage pdf
