Re: Modifying the save path in an NSDocument based application
Re: Modifying the save path in an NSDocument based application
- Subject: Re: Modifying the save path in an NSDocument based application
- From: Pax <email@hidden>
- Date: Wed, 18 Sep 2013 20:54:13 +0100
Okay, the plot thickens. I've now updated my app for the app store - sandboxing is now enabled. Sandboxing breaks the save path modification, and particularly my creation of a folder:
if(![fileManager createDirectoryAtPath:directory
withIntermediateDirectories:NO
attributes:nil
error:&error])
{
NSLog(@"Failed to create directory \"%@\". Error: %@ - this save will most likely fail entirely.", directory, error);
}
else
{ ... }
With sandboxing enabled, the creation of the directory always fails - unless the user opts to save in the Downloads directory. Most odd.
The user can choose to save an undecoded version of the file wherever they like. I have set read/write access for the Downloads Folder - which probably explains this. How can I get read/write access to wherever the user chooses to extract the files (most likely Documents, loose in their home folder, or the desktop?)
On 17 Sep 2013, at 15:20, Jerry Krinock <email@hidden> wrote:
>
> On Sep 17, 2013, at 07:49:56, Pax <email@hidden>
> wrote:
>
>> I thought that this would be nice and simple
>
> No. Overriding anything in the AppKit document architecture is playing with fireworks, especially since Auto Save and Versions. To be safe, when you're "done", retest all of the functions: Duplicate, Rename, Move To, Browse All Versions, etc., in all OS X versions you're deploying to.
>
> On 2013 Sep 17, at 06:41, Steve Mills <email@hidden> wrote:
>
>> You might try overriding saveToURL:ofType:forSaveOperation:completionHandler: instead. writeToURL is at a very low level in the save operation, and if you look at the stack, I bet writeSafelyToURL:ofType:forSaveOperation:error: is one of the callers of writeToURL.
>
> Steve's advice looks good to me. For a picture of the Save operation, in Xcode's Documentation browser, check out
>
> Document-Based app Programming Guide for Mac > Alternative Design Considerations > Message Flow in the Document Architecture > Saving A Document > Figure 6-6 at the bottom of the page
>
> Supposedly this document has recently been updated to reflect Auto Save and Versions, but I haven't verified that.
> _______________________________________________
>
> Cocoa-dev mailing list (email@hidden)
>
> Please do not post admin requests or moderator comments to the list.
> Contact the moderators at cocoa-dev-admins(at)lists.apple.com
>
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden