Keith wrote:
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?)
Yes, that sounds like a good approach.
I usually try to separate code, UI, and data as much as practical so
that changes to one minimize impact on the others. With your separating
those settings into another stack file it seems you'll have that done well.
--
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
