Re: Bug in PDFKit's PDFDocument attributes?!
Re: Bug in PDFKit's PDFDocument attributes?!
- Subject: Re: Bug in PDFKit's PDFDocument attributes?!
- From: "Adam R. Maxwell" <email@hidden>
- Date: Tue, 23 May 2006 07:37:38 -0700
On May 23, 2006, at 07:21, Jim Correia wrote:
On May 23, 2006, at 6:18 AM, Alexander Griekspoor wrote:
However, when I build the app using the above predefined values, I
get the following error:
[Session started at 2006-05-23 11:53:48 +0200.]
ZeroLink: unknown symbol '_PDFDocumentAuthorAttribute'
So somehow, the values are not defined.
You aren't linking to PDFKit. Add its parent umbrella framework,
Quartz.framework, to your project.
It won't help. Those symbols are undefined.
But that's not all, it turns out that the CreationDate objects are
NOT like the documents state of type NSString but of type NSDate !?
It appears that the documentation disagrees with the header
comments (which based on your experience, *are* correct.)
The documentation is updated frequently and in my experience
problems like this are addressed fairly quickly if you file a bug
pointing them out.
I filed it 3 months ago after my code raised an exception from
treating NSDate as NSString.
One other PDFKit bug that I ran across: don't use -[PDFDocument
writeToURL:], since it returns YES even if it fails (I filed this as
well). Convert first to NSData and then write that to disk.
Adam
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden