LiveCode Forums.

Hi, I'm developing my first Windows & Apple app in LiveCode and am now starting to appreciate its rapid development capabilities. Like many other experienced developers from a traditional edit-compile-run environments, I have taken some time to understand the persistent nature of LiveCode values from session to session. I've read tutorials like use of alternative to global variables as well as the tutorial on launching and saving a separate main stack, and, of course, forum entries.

I appreciate if someone could summarise which values in the main application (as opposed to external files and databases) will 'stick' between multiple executions of the same deployed application. This will check my understanding.

Of course, I'd appreciate any other advice to manage the persistency better. Thanks, Alex

alexGAzLSp wrote:I appreciate if someone could summarise which values in the main application (as opposed to external files and databases) will 'stick' between multiple executions of the same deployed application.

None. All modern operating systems prevent an executable from being able to modify itself for security purposes.

Any data you want to store between sessions will have to be done outside the app - this article provides some useful tips:
http://livecodejournal.com/tutorials/sa ... ution.html

Excellent, thank you for the reference. Alex