Protected stacks in 2.61 (was For goodness sake!)

[Robert Brenstein]

>
>Good points.  I'll add a preference for that in the MC IDE.
>
>Of maybe better:  how about the ability to define a stack to be used 
>as a template for new stacks?  That way we can handle destroyStack, 
>alwaysbuffer, rect, and anything else we want exactly as we want it.
>
>Worth pursing a change to the default behavior of the engine?
>I'd love to see the alwaysBuffer set to true as well....
>

Yes, yes, being able to define an alternative template stack would be 
great (aside from setting destroy on in the built-in one, and I'd 
vote for setting buffering on as well).

Robert