Array Properties in a Standalone

[Bob Sneidar]

I mean the checkbox "Move Substacks into individual stack files" is UNCHECKED and the stacks are NOT substacks of the original stack. When I open the package (OS X), I see that in the MacOS folder there is an executalbe file called Forms Generator (which is what I told the splash stack the app was called so that makes sense). In the Resources/_MacOS folder I see eack substack as an individual file with the extension set to .rev. The Forms Generator stack (the original mainstack but NOT the splash stack) has the extension .livecode. So do the included libraries. Curiously, the Forms Generator stack is 0 bytes big! The other stacks are of some size.

When you say the stacks cannot be modified, that may be however I see that I have read/write permissions to the substacks (the customers.rev for example). I was also successful in copying a file to the folder the substacks are in. Mind you these are folders IN the application package.

Also if I cannot modify one of these substacks then properties as a means to save persistent values between launches is a complete bust! I make extensive use of this. I really do not want to have to write this data out to a file because some of it is values I do not want the user to gain access to. At least not easily.

I am going to test this and let you know. I am going to increment a numeric property in the customers stack and pop a dialog each time I launch it displaying the value.

Bob S


On Jan 12, 2017, at 12:13 , J. Landman Gay via use-livecode <use-livecode at lists.runrev.com<mailto:use-livecode at lists.runrev.com>> wrote:

On 1/12/17 12:25 PM, Bob Sneidar via use-livecode wrote:
Even though in the standalone settings I have the option to save
substacks as individual stacks unchecked, it does it anyway. It just
puts them in the app package instead of in another folder.

Did you mean "checked"? If checked, that option will extract substacks and save them as independent mainstacks. If not checked, they remain substacks. If LC isn't behaving that way it's a bug.

In either case, you can't write to the app bundle. If you want to save data, you need to copy the stacks to a writable location on first launch. The standalone builder can't know where you will want to save those stacks, and always places them into a folder you can access with specialFolderPath("resources").

--
Jacqueline Landman Gay         |     jacque at hyperactivesw.com<mailto:jacque at hyperactivesw.com>