AW: Looking for a common service friendly stack design

[J. Landman Gay]

Tiemo Hollmann TB wrote:

> and you do it just with a go, without closing or destroying the first stack
> file? Do you need the first one again, or what is the reason not to destroy
> it?

The "destroystack" property is permanent and stored with the stack. You 
only need to set it once during development, and the property will be 
persistent. It does not need to be in a script. If destroystack is true, 
just closing the stack will remove it from RAM. If destroystack is 
false, closing the stack keeps it in RAM so that the next time you open 
it, it opens faster.

The destroystack property only applies to main stacks in the IDE. 
Substacks can have the property set to true, but they always remain in 
RAM anyway.

If a standalone's mainstack has destroystack set to true, the standalone 
will not quit if any substacks are still open. The main stack will also 
remain in RAM in that case, since the stackfile is still open as long as 
a substack is open. In a standalone, the destroystack property of the 
mainstack is of little importance, since quitting a standalone purges 
RAM anyway.

If a standalone opens other independent stacks, then their destroystack 
property does matter, just as it does in the IDE.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com