Temporary custom properties

Mark Swindell mdswindell at cruzio.com
Thu Feb 14 17:20:39 EST 2008

You could create a field, graphic, or button, you decide, on opening  
your stack and set its custom properties to whatever you want.  Then  
on closestack you could delete the object.

You could also set the cProperty1, cProperty2, cProperty3 of an  
existing objectX (whatever object you want... card, stack, button,  
etc) to myValues, and then on closing the stack set the  cProperty1,  
cProperty2, cProperty3 of objectX back to empty.

But out of curiosity, why not use globals?


On Feb 14, 2008, at 2:05 PM, Russell Martin wrote:

> Hey, does anyone have a suggestion about what is the best kind of
> (non-visible) object to create on the fly for temporarily storing
> custom properties?
> In other words, I want to use custom properties like global variables,
> but I want to put them in something that only exists during program
> execution and that won't get saved with my project.
> Or, should I be using something besides custom properties for keeping
> global, transient values that the program only needs during execution?
> ____________________________________________________________________________________
> Never miss a thing.  Make Yahoo your home page.
> http://www.yahoo.com/r/hs
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution


More information about the Use-livecode mailing list