Re: More PDFView mysteries...
Re: More PDFView mysteries...
- Subject: Re: More PDFView mysteries...
- From: Graham Cox <email@hidden>
- Date: Fri, 15 Jun 2012 10:08:02 +1000
On 15/06/2012, at 8:15 AM, Matthew Weinstein wrote:
> It almost feels like the windowControllerDidLoadNib is happening too quickly (or something).
Note what that method literally tells you - the window controller loaded the nib. That doesn't mean that the actual window was instantiated yet (with all its views). A window controller lazily loads the window when it is actually required, which is a bit later. You can use the controller's windowDidLoad method to find out when that has happened.
The probable reason this is different on Lion is because NSDocument is a very different beast on Lion. It is often invoked on a background thread and various interface-less document objects are made to support Versions and Autosaving. It's a rather complex situation on Lion which *appears* to assume a very great deal about how your app has subclassed NSDocument. For example, when browsing Versions, each version you see is an actual instance of your NSDocument subclass complete with its window - it's not just the snapshot image you might have thought. Scary stuff.
--Graham
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden