Thanks to everyone for your input...
Richard: I have a pretty large stack with lots of graphics and controls... I
could just save the stack to save the settings, but each stack would be
quite large in size. Also, if I need to upgrade the software, all of the
saved stacks would need to be updated accordingly.
I have decided to create a separate stack to transfer the custom properties
back and forth from, saving each of these stacks as a "data stack" so to
speak. The data stack will only contain the custom settings and no actual
controls... Seems to be working good. (I presume this is the way to go?)
Thanks again,
- Boo
-----Original Message-----
From: Richard Gaskin
Sent: Thursday, December 29, 2011 11:30 AM
To: use-livecode@lists.runrev.com
Subject: Re: Sample stack demonstrating how to obtain all properties and
customproperties of a stack?
Bob Sneidar wrote:
It seems like it would be easier to clone a stack, then reset everything
in it, or just keep a copy of a virgin stack around. You would have to
update it every time you made any changes to the original though.
That's been my experience as well. The stack file format is so compact
and convenient that it's hard to beat for most project management tasks.
Keith, what is the problem you were looking to solve?
--
Richard Gaskin
Fourth World
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode developers: http://www.LiveCodeJournal.com
LiveCode Journal blog: http://LiveCodejournal.com/blog.irv
_______________________________________________
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
_______________________________________________
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
