Re: I think I screwed up Core Data multi-threading rules.

2017-02-25 Thread Quincey Morris
On Feb 25, 2017, at 14:58 , Daryle Walker wrote: > > I thought the entire AppKit, which includes NSDocument, runs only on the main > thread. The exceptions are methods that specially state that they have a > multi-threaded mode. Much stuff in AppKit must be called on the main thread, yes, and

Re: I think I screwed up Core Data multi-threading rules.

2017-02-25 Thread Daryle Walker
> On Feb 23, 2017, at 10:43 PM, Quincey Morris > wrote: > > On Feb 23, 2017, at 18:25 , Daryle Walker > wrote: >> >>>override func save(to url: URL, ofType typeName: String, for >>> saveOperation: NSSaveOperationType, completionHandler: @escaping (Error?) >>> ->

Re: I think I screwed up Core Data multi-threading rules.

2017-02-23 Thread Quincey Morris
On Feb 23, 2017, at 18:25 , Daryle Walker wrote: > >>override func save(to url: URL, ofType typeName: String, for >> saveOperation: NSSaveOperationType, completionHandler: @escaping (Error?) -> >> Void) { >>// Save the message data to the store so any background contexts can >> rea

Re: I think I screwed up Core Data multi-threading rules.

2017-02-23 Thread Daryle Walker
> On Feb 23, 2017, at 1:56 AM, Daryle Walker wrote: > > I naively thought this was OK, multi-threading wise. It worked before I added > the “canAsynchronusly…” method to say TRUE for my main file type. When that > method is added, the save hangs the program. > >>override func data(ofType