Mac Desktop App - No Longer Save to the Engine/Resourses Folder?

Bob Sneidar bobsneidar at iotecdigital.com
Thu Feb 7 10:32:17 EST 2019


It's my understanding that permissions to files in the package of a standalone are read only for the user, the admin group and the everyone group. The stack will work in memory, but you cannot save it without write permissions. 

What you might consider is a terminal script you run on your standalones that will change permissions to the resources folder so that everyone can write. Not sure how sandboxing will come into play if you do that. 

As stated in many prior posts, it's better to keep all your custom settings that need to be saved between sessions in a prefs file or a database. Otherwise you set yourself up for a lot of support calls trying to deal with user permissions and sandboxing both now and in the future. 

Bob S


> On Feb 6, 2019, at 17:04 , Sannyasin Brahmanathaswami via use-livecode <use-livecode at lists.runrev.com> wrote:
> 
> I have to update some in house production app for  Mac. To 64 bit... 
> 
> Used to Be: I could create a standalone, like a little "splash" engine and copy a separate stack to the engine location for it boot and save that stack.  
> 
> Now the stack is store in the app package to 
> 
> /Contents/Resources/_MacOS/InfoWizard.livecode
> 
> A simple script upgrade to "the effective name of this stackloader" to 
> 
> on preopenstack
>   set the loc of this stack to the screenloc
> end preopenstack
> 
> on openStack
>   put specialFolderPath("resources") into tPath
>   put "/InfoWizard.livecode" after tPath
>   wait 60 ticks
>    hide  stack "infoWizard Loader"
>    go  stack url ("binfile:" & tPath)
> end openStack
> 
> Works.... but I cannot save to that "external" stack.
> 
> Is this no longer allowed by Apple?  If not, will the only option (like on mobile) be to copy the stack from the standalone "out" to the documents folder and boot if from there and *then*  OSX will let me save data to it? (custom properties)?
> 
> BR





More information about the Use-livecode mailing list