Re: Core Data and the Application Delegate
Re: Core Data and the Application Delegate
- Subject: Re: Core Data and the Application Delegate
- From: "Sean McBride" <email@hidden>
- Date: Fri, 24 Apr 2009 15:27:16 -0400
- Organization: Rogue Research Inc.
On 4/23/09 8:37 PM, Jon Gordon said:
>I'm having trouble understanding how to do certain things with the
>application delegate in a document-based application that uses Core
>Data. Or maybe I'm understanding things perfectly well, but I don't
>like the logical conclusion. But I digress.
>
>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.
>
>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. And in such cases, providing my own delegate breaks Core Data
>functionality that I'd otherwise get for free.
>
>Am I right about this?
I don't believe so. Why do you believe this? In any case, you can
check yourself by asking NSApplication what its delegate is.
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
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