Re: Best Advice for accessing App Delegate's Managed Object Context

> On 2015 Oct 18, at 13:07, Michael de Haan  wrote: > > I got rid of all the notification code, and substituted this in each > controller that needed access to the managedObjectContect > >> Just show me how to do that in Swift :) > > lazy var

Re: Best Advice for accessing App Delegate's Managed Object Context

Well, there is something to be said for simplifying the code!!! I got rid of all the notification code, and substituted this in each controller that needed access to the managedObjectContect > Just show me how to do that in Swift :) lazy var managedObjectContext:NSManagedObjectContext! = {

Re: Best Advice for accessing App Delegate's Managed Object Context

On 2015 Oct 18, at 12:18, Michael de Haan  wrote: > I have not worked that much with SplitViewControllers, The fact that it is a split view controller is not relevant here. You’d have the same issue with any kind of controller. > The immediate hurdle was to supply each

Re: Best Advice for accessing App Delegate's Managed Object Context

> > It looks to me like you are instantiating a window controller, not a split > view controller. But that’s a better idea anyhow. Correct… the WindowController “contains” the SplitViewController > >> > > By “context”, do you mean managed object context? correct again. > Alarm

Best Advice?

I am using a separate, second “standAlone" Window to display a SplitViewController. Design is StoryBoard, for an OS X application. From appDelegate, I instantiate the SplitViewController in “applicationDidFinishLaunching" let storyBoard = NSStoryboard(name: "Main", bundle: nil)

Re: Best Advice for accessing App Delegate's Managed Object Context

> On 2015 Oct 18, at 05:05, Michael de Haan  wrote: > > I am using a separate, second “standAlone" Window to display a > SplitViewController. Design is StoryBoard, for an OS X application. > From appDelegate, I instantiate the SplitViewController in >