Re: Core Data and the Application Delegate
Re: Core Data and the Application Delegate
- Subject: Re: Core Data and the Application Delegate
- From: mmalc Crawford <email@hidden>
- Date: Fri, 24 Apr 2009 18:27:13 -0700
On Apr 23, 2009, at 5:37 PM, Jon Gordon wrote:
In a normal (i.e., non-Core Data) document-based application, as I
understand it, one can modify certain functions by providing a
delegate to the instance of NSApplication. For example, to keep the
application from opening a blank document at launch, I can have a
delegate that implements applicationShouldOpenUntitledFile: and
always returns NO.
Yes.
But I understand (I think) also that, in a Core Data document-based
application, the application delegate is set to one provided by Core
Data.
No.
And in such cases, providing my own delegate breaks Core Data
functionality that I'd otherwise get for free.
No.
Am I right about this?
No.
If so, what's the best way to make changes (like not opening the
blank document at startup) that would, absent Core Data, be made by
providing an application delegate? And where's the best
documentation for this?
What happened when you created a standard Core Data document-based
application and added an application delegate that implemented
applicationShouldOpenUntitledFile:?
mmalc
_______________________________________________
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