Protected stacks in 2.61 (was For goodness sake!)

[Richard Gaskin]

Ken Ray wrote:
> On 9/19/04 12:40 PM, "Robert Brenstein" <rjb at robelko.com> wrote:
> 
> 
>>>On 9/17/04 9:54 AM, Robert Brenstein wrote:
>>>
>>>
>>>>Not instating password protection upon close is yet another issue
>>>>and I will Bugzilla it as well. It is not new to 2.6.1 but it did
>>>>not check how far back it goes.
>>>
>>>Not a bug, and it goes back to the beginning of time. Password
>>>protection takes place when the stack loads. If you have the
>>>destroystack set to true, closing and reopening will set password
>>>protection. If you have destroystack set to false (which is the
>>>IDE's default setting for new stacks) then reopening the stack
>>>simply displays the copy already in memory and does not reload it.
>>>
>>>--
>>>Jacqueline Landman Gay         |     jacque at hyperactivesw.com
>>>HyperActive Software           |     http://www.hyperactivesw.com
>>
>>
>>Ah, yes, gotcha.
>>
>>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
  ___________________________________________________________
  Ambassador at FourthWorld.com       http://www.FourthWorld.com