On Apr 24, 2009, at 8:47 PM, Jon Gordon wrote:
On Apr 24, 2009, at 4:40 PM, Jason Foreman wrote:
On Apr 23, 2009, at 7:37 PM, Jon Gordon wrote:
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
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
On Apr 24, 2009, at 7:47 PM, Jon Gordon wrote:
On Apr 24, 2009, at 4:40 PM, Jason Foreman wrote:
On Apr 23, 2009, at 7:37 PM, Jon Gordon wrote:
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. An
On Apr 24, 2009, at 4:40 PM, Jason Foreman wrote:
On Apr 23, 2009, at 7:37 PM, Jon Gordon wrote:
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 break
I believe it to be so because of some things I found while Googling to
look for the answer. I even found one poster to some list who claimed
that his Core Data app worked perfectly well until he set his own
application delegate, at which point it stopped working perfectly well.
On the othe
On Apr 23, 2009, at 7:37 PM, Jon Gordon wrote:
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 fo
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 n
