Thanks for that very interesting observation Jacque. Since reading your mail
I’ve been using this new arrangement, but I **think** I’ve just noticed that
generates a path with a “/“ at the end in a standalone, but omits the “/“ when
in the IDE. Maybe I’m just a bit tired - it’s late here. If it’s true though,
it must be a bug.
Someone might like to test this, or I will tomorrow.
> On 14 Oct 2016, at 07:22, J. Landman Gay <jac...@hyperactivesw.com> wrote:
> On 10/13/16 6:17 PM, Curtis Ford wrote:
>> I've just made a new module for this client with largely the same code;
>> now LiveCode 8.1 saves the files in Contents > Resources > _MacOS > media.
>> So the standalone doesn't find the sound files unless I move them
>> manually after doing 'show contents' in the Finder.
>> Is this a bug, or should I be setting the path differently now?
> Apple now requires all resources to be in a separate folder. Nothing is
> allowed in the engine folder except the executable. We now have a new
> specialFolderPath("resources") to access that folder.
> Instead of parsing a path from the engine folder, use:
> specialFolderPath("resources") & "/media/" & gMediaPath
> Everything in the Copy Files pane of the standalone settings now gets put
> into specialFolderPath("resources").
> In the IDE, the resources folder is the one that contains your mainstack.
> This is handy because you can keep the same hierarchy in your working folder
> and the specialFolderPath still works there.
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
> use-livecode mailing list
> Please visit this url to subscribe, unsubscribe and manage your subscription
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription