And persistent they are, if the stack file the custom properties are in is saved with a simple save command. A stack file can hold any number of custom properties. Even arrays, stacks and images can be turned into a custom property and restored. Persistence = a file somewhere!The file can be in any directory that can be written to by the user. On a macintosh, it's especially easy, as the .app package provides a place that files can be read and written to but yet out of reach for most users.
Stephen Barncard ------------------------- San Francisco 2009/2/13 Robert Sneidar <slylab...@me.com> > 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 modified >> 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@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution