Re: NSDocument and the dreaded "The location of the document XXX cannot be determined"

Hi Jerry, After adding a "Save As Move" command to an application, I was getting a different but related warning, something like "Document has been moved, do you really want to save it to a new location?" The solution was to sprinkle in an extra invocation of saveToURL:ofType:forSaveOper

Re: NSDocument and the dreaded "The location of the document XXX cannot be determined"

On 1 apr 2010, at 13.50, Martin Wierschin wrote: > Any help on this would be much appreciated; I've spent way too long on this > silly thing already. Please file a bug report where you outline what you're trying to do: j o a r _

Re: NSDocument and the dreaded "The location of the document XXX cannot be determined"

On 2010 Apr 01, at 13:50, Martin Wierschin wrote: > I should say that I've overridden my NSDocument's save methods Indeed, you're playing with a highly crafted system there. After adding a "Save As Move" command to an application, I was getting a different but related warning, something like "

NSDocument and the dreaded "The location of the document XXX cannot be determined"

Hello everyone, I'm banging my head against a problem with my NSDocument subclass. The first time a document is resaved (eg: a regular NSSaveOperation that overwrites an existing file) all goes well. If the document remains open and is later resaved again, Cocoa displays a warning that: The