Re: NSController controllerEditor:didCommit :… exception

2010-11-15 Thread Kyle Sluder
On Mon, Nov 15, 2010 at 12:00 PM, vincent habchi wrote: > My app is neither very simple, nor very complex. Your first solution should > be more than adequate. > > Thanks a lot, have a great day! No problem. Just keep in mind that by avoiding NSWindowController, you lose its automatic breaking of

Re: NSController controllerEditor:didCommit :… exception

2010-11-15 Thread vincent habchi
Kyle: > If your app is simple enough, your app delegate could initialize the MOC and > act as the nib's File's Owner. In more complicated applications, I would > instead recommend the app delegate still be in charge of creating the MOC, > but also creating an NSWindowController that loaded the

Re: NSController controllerEditor:didCommit: … exception

2010-11-15 Thread Kyle Sluder
On Nov 15, 2010, at 5:32 AM, Vincent Habchi wrote: > > Yes, the MOC is provided through a binding to the AppController, itself part > of the NIB. But the MOC iVar is set to nil until the user successfully opens > a persistent store file. So I imagine the init code for the NSArrayController >

Re: NSController controllerEditor:didCommit :… exception

2010-11-15 Thread Vincent Habchi
Kyle: > The main menu nib is kind of funny. It's loaded differently (or at > least at a different time) than the other nibs. It's much more > sensitive to timing issues like this. > > Who provides the MOC for the controller (another object in the nib?), > and how is it provided (bindings, -setMan

Re: NSController controllerEditor:didCommit :… exception

2010-11-14 Thread Kyle Sluder
On Sun, Nov 14, 2010 at 11:10 PM, vincent habchi wrote: > > Quincey, Kyle: > > >> While it is true the MOC is not initialized at this point, I don't see > >> what could cause this message appear at such an early stage. Can it be > >> linked somehow with the initialization of a static object embe

Re: NSController controllerEditor:didCommit :… exception

2010-11-14 Thread vincent habchi
Quincey, Kyle: >> While it is true the MOC is not initialized at this point, I don't see what >> could cause this message appear at such an early stage. Can it be linked >> somehow with the initialization of a static object embedded in the >> "MainMenu" NIB? > > If, as it happens, your MainMen

Re: NSController controllerEditor:didCommit :… exception

2010-11-14 Thread Quincey Morris
On Nov 14, 2010, at 03:32, vincent habchi wrote: > While it is true the MOC is not initialized at this point, I don't see what > could cause this message appear at such an early stage. Can it be linked > somehow with the initialization of a static object embedded in the "MainMenu" > NIB? If, a

Re: NSController controllerEditor:didCommit: … exception

2010-11-14 Thread Kyle Sluder
On Nov 14, 2010, at 3:32 AM, vincent habchi wrote: > Hi everybody, > > this is a minor annoyance but I'm still puzzled about it. > > When I launch my application, after -applicationWillFinishLaunching: > completes, I get an exception started by -[NSController > controllerEditor:didCommit:cont

NSController controllerEditor:didCommit:… exception

2010-11-14 Thread vincent habchi
Hi everybody, this is a minor annoyance but I'm still puzzled about it. When I launch my application, after -applicationWillFinishLaunching: completes, I get an exception started by -[NSController controllerEditor:didCommit:contextInfo:]. I cannot get a decent traceback to pinpoint what object