Arrays and Custom Props
bobs at twft.com
Mon Feb 16 13:56:43 EST 2009
If this is another duplicate from me I apologise. My email keeps
defaulting to the wrong account and I don't catch it in time.
Calvary Chapel CM
On Feb 13, 2009, at 4:24 PM, Robert Sneidar wrote:
> WHOA THERE TONTO! I thought the whole idea to properties was
> persistence?? That means that I cannot save, for instance, the
> database settings a user entered? I have to create an external file
> for all of that? And so many card and object properties in my app
> DEPEND on persistence through runtime. This means that I have to put
> a kabosh on the whole project!
> Say it ain't so Sam!
> Bob Sneidar
> IT Manager
> Logos Management
> Calvary Chapel CM
> On Feb 13, 2009, at 3:53 PM, Jim Ault wrote:
>> I think of arrays as..
>> Arrays, like variables, evaporate on quitting,
>> Custom properties, like button names, are stored in the stack file.
>> (note: this is not true for compiled apps since they cannot be
>> You store data in custom properties before compiling and they
>> become part of
>> your app, such as jpgs, sounds, even whole stack files)
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
More information about the Use-livecode