Thanks guys, turns out it was a stupid mistake on my end!
I'll only say this: If you're trying to prevent your app from creating
a new document when it launches, make sure your App delegate isn't
getting instantiated in your Document's nib! :P
(Oh and Andy, you're absolutely right about the
On Feb 3, 2009, at 3:06 PM, Jean-Nicolas Jolivet wrote:
I tried overriding the applicationShouldOpenUntitledFile in my App
delegate
P.S. This may sound nitpicky, but I suspect you weren't actually
*overriding* the method but merely *implementing* it. You're only
overriding a method if it
On Feb 3, 2009, at 6:02 PM, Jean-Nicolas Jolivet wrote:
yeah I just wrote it from memory in my email, in my app, I actually
copied the method declaration from the docs...
That's the way to do it IMO for any method name that I don't trust
myself to remember. :)
FWIW, I made a quick Core Dat
On 2/3/09 6:02 PM, Jean-Nicolas Jolivet said:
>yeah I just wrote it from memory in my email, in my app, I actually
>copied the method declaration from the docs... (I'm 100% sure it's not
>a typo/delegate connection problem)
applicationShouldOpenUntitledFile: works in my document-based Core Data a
yeah I just wrote it from memory in my email, in my app, I actually
copied the method declaration from the docs... (I'm 100% sure it's not
a typo/delegate connection problem)
On 3-Feb-09, at 3:20 PM, Andy Lee wrote:
On Feb 3, 2009, at 3:06 PM, Jean-Nicolas Jolivet wrote:
I tried overridin
On Feb 3, 2009, at 3:06 PM, Jean-Nicolas Jolivet wrote:
I tried overriding the applicationShouldOpenUntitledFile in my App
delegate
Is this a typo in your email, or did you leave out the colon in your
method name? The method should be declared like this:
- (BOOL)applicationShouldOpenUntitl
I tried overriding the applicationShouldOpenUntitledFile in my App
delegate to prevent the creation of new documents when my app is
launched, however it doesn't seem to be working (the method is never
invoked).
Could this be because I'm using a Core Data Document-based app? If so,
is ther
