It may be appropriate to bring up again the default setting of the destroy property for new stacks. Should it be made on or remain off?
Made on by default - more often than not, you want it set to true, IMHO.
In my own work it usually makes little difference.
What are the benefits each way?
-- Richard Gaskin
The first thing I always do when creating new stacks is to set destroy on for the reasons that Ken outlined plus password protection. In fervor of testing the cloning, I forgot to set it and was surprised that password protection was not working.
In such a circumstance the only risk is others using your machine during the same MC session. The password is preserved on disk regardless of the state of the destroyStack property.
-- Richard Gaskin Fourth World Media Corporation ___________________________________________________________ [EMAIL PROTECTED] http://www.FourthWorld.com _______________________________________________ metacard mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/metacard
