On Mon, Apr 27, 2009 at 11:55 AM, Joe Lewis Wilkins <[email protected]> wrote: > OK, now under what circumstances might we want to store a stack in either a > Custom Property or a Var? These aren't things we'd want or have to do in HC. > At least I never did in the many hundreds of stacks I created and used. > There must be some sort of unique things that can be done under these > circumstances that cannot be done with "ordinary" stacks, but still not > having adopted CPs, they are just not obvious to me. TIA,
One possibility is a document based app, where you need to create a new stack every time the user wants a new document. You store a template stack in a custom property and spit it out whenever needed. Another idea is for saving data or settings. Since you cannot save directly to the standalone (unless you have separate sub-stacks), you could have a prefs stack stored in a CP. When you launch the app, check if the stackfile exists and if so, read the settings from it. If it doesn't exist, create one with default settings from your custom property. Cheers, Sarah _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
