Protected stacks in 2.61 (was For goodness sake!)

[Robert Brenstein]

>>>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.

Robert