On Tue, May 6, 2008 at 9:06 PM, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> I assume it's not OK to create a second controller in the preferences NIB
> bound to the same managedObjectContext.
I wouldn't assume that -- as long as all your GUI code is kept to the
main thread, there shouldn't be any
I have an array of objects. The main application loads the objects via
Core Data. The controller is in the main NIB. Now I have a separate
NIB for the preferences. In this this NIB I have a NSTableColumn I
want to bind to the controller for the objects. But the controller for
the objects is
