Is it a library that will not be edited programmatically at runtime? If not,
then that is the place it belongs.
> On Mar 28, 2017, at 06:07 , Tiemo Hollmann TB via use-livecode
> Creating a standalone on MacOS 10.12 with LC 8.1.3, LiveCode
I think that's right, Apple enforces this rule.
The standalone builder will move files to a Resources folder when it
builds the app. For backward compatibility, scripts that reference the
engine folder are redirected to the Resources folder automatically.
On 3/27/17 1:22 PM, Bob Sneidar via
To my understanding, it's a requirement in accordance with Apple's sandboxing
policies, if you want an executable to be able to make changes to files inside
the executable bundle. The way it's supposed to work, no application is allowed
to write or modify anything in the old location where the
thanks for that hint. Seems i have missed that part..
> Am 15.03.2017 um 07:44 schrieb J. Landman Gay via use-livecode
> On 3/14/17 6:58 PM, Matthias Rebbe via use-livecode wrote:
On 3/14/17 6:58 PM, Matthias Rebbe via use-livecode wrote:
is it correct when the standalone settings of an stack are set to
move substacks into individual stack files that under Mac OS X the
substacks in an compiled app (e.g. test.app) are stored