Stacks can be opened many ways. In most of my projects I only manually
open one stack in the IDE, and the scripts in that stack may load as
many as a dozen others.
To satisfy the request the engine would have to intercept all attempts
to open stacks, or maybe just the save command, and then intervene based
on the value of some flag.
Ouch. Sounds like a lot of work for the team, and one more deep task
for all of us to test.
Seems simpler to just make a copy of your work folder before using a
pre-release build. Leaving us in control is the surest way to protect
all possible ways a stack file can be altered.
--
Richard Gaskin
Fourth World
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode developers: http://www.LiveCodeJournal.com
Follow me on Twitter: http://twitter.com/FourthWorldSys
_______________________________________________
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
