I'm not sure what I'm doing wrong when adding a "selection" property to my document class so the user can get and set the selected assets. When I run: tell application "Image Chest" tell document

The problem was caused by a merge. Even though the mapping model LOOKED correct in the Xcode mapping model editor, the underlying data was bogus. So yeah, don't work on a mapping model (or probably

During development of a new version of my app, I added a new data model version with one additional attribute on one of the entities, and a mapping model to set the default value of that new required

I got it to work by calling the window's restoreStateWithCoder: instead of the document's. In my tests, it takes care of this and repositions the window so it's on the currently available screen[s]

No, the window autosave name predates state restoration by a lot of years. IIRC, the behavior breaks down like this: 1. Window restoration (if enabled) overrides everything else, for windows that are

Did something change recently? frameautosave has historically been the way to save a window’s frame, regardless of when the window was opened. Maybe you should take a second look. If you have a

From what I've experienced and read, that only helps for reopening docs on app launch, not on opening docs once launched. The OS only stores info for docs that were open when the app exits so it can

Can't you just set NSWindow.frameAutosaveName? Or does NSDocument get in the way of that? - Jon

Doc and window restoration is great when relaunching the app, but I also want each document's window to open to their last frame when the user opens documents. I can not find the right place to make

There’s some mention of it here. https://stackoverflow.com/questions/46099940/credstore-perform-query-error/48961852

It looks like you are being limited for making too many requests in one period of time. That’s my guess.

If you are modifying the object, I believe you should be doing this in: createDestinationInstances(forSource:in:manager:) This has always worked for me. The validation method looks like a keep/don’t

No, I wasn't sure if that was necessary. One would hope that the act of migration will save the migrated data to the store without the developer having to do anything. It doesn't say that in the

I am building an app that accesses the Library of Congress Online Card Catalog. At this point, I'm mainly running from the Simulator. And sometimes when I issue the GET query, I get the following

Do you call save on the context somewhere? I’ve not needed to use a mapping like this yet but it seems like if you’re changing attributes you’d want to save. Jim Crate

In my Core Data model, I've added a 2nd version with a new attribute. This attribute needs to be initialized to a sequential value upon migration from the old version. So I'm using a mapping model and

It must have something to do with NSTextFields (or any view in general) whose value uses bindings. The text fields and the progress bar in this sheet all use bindings to set their values. If I add a

Control has returned. Changing a UI object has to be done from the main thread, so I'm doing it from dispatch_async(dispatch_get_main_queue(), …), and I've verified that the block does get run very

Has control returned to your main event loop, or are you still doing some kind of processing during the delay time? When you change the button name, etc, is that all being done from the main thread

I'm putting up a sheet from a nib to display progress while I process things. When processing is done, I change the button name and ensure the progress bar is set to max. At that point, one of the