well if one were setting all of the properties of a stack, they'd have to be set to another stack.
set the properties of stack "b" to the properties of stack "a" Easier to copy the stack.Can all the properties be placed into a variable? I think some props will be left out by design, otherwise objects would blow up. A while ago I experimented with saving complete descriptions of livecode objects as text with some success. It was possible to get most, but not all properties in repeat loops, however I found that the recursive code needed to bury within groups of groups was just too time consuming to be worth it. It was pointless to continue, the packaging I desired was much more easily handled and portable with the Livecode containers. On 28 December 2011 13:17, Bob Sneidar <b...@twft.com> wrote: > I meant all at once as in set the properties of this stack to > theSavedProperties > > Bob > > > On Dec 28, 2011, at 10:16 AM, Mark Wieder wrote: > > > Bob- > > > > Wednesday, December 28, 2011, 8:31:54 AM, you wrote: > > > >> Putting the standard properties back is a bit trickier though. I > >> don't think you can set the properties of a stack. > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- Stephen Barncard San Francisco Ca. USA more about sqb <http://www.google.com/profiles/sbarncar> _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
