populating stack with field

Trevor DeVore lists at mangomultimedia.com
Thu Jul 1 13:35:58 CDT 2004

On Jul 1, 2004, at 11:12 AM, Cubist at aol.com wrote:
> ...
>    If you jump thru this particular hoop, the benefit is that your 
> real app
> is "merely" a document, *not* an executable file -- and that means you 
> *can*
> save any & all changes that are made to your real app.
>    Hope this helps...

Just an additional note.  If you save state in your application by 
saving the program stack each time the user quits be aware that this 
will not work on NT/2000/XP and OS X systems where the user does not 
have administrative privileges.

What Revolution probably needs are some functions for getting/setting 
preferences that would do the right thing on each platform (Registry on 
Windows, pList on Mac, etc.).  You of course can roll your own that 
just stores preferences in a stack file that you save in a folder that 
all users can write to.

Trevor DeVore
Blue Mango Multimedia
trevor at mangomultimedia.com

More information about the use-livecode mailing list