Removing a stack from memory - is this a bug?

[Stephen Barncard]

The management of multiple visible stacks in scripts seems to be, for 
me, one of the most agonizing things to "get" and work with in Rev.

I (or someone) need to make a demo stack or one-page list of 
conditions, states, gotchas, that relate to multiple stacks.

  and the use of go,modal,modeless,close,invisible,reloadStack etc.
also DELETE STACK, DELETESTACK, DESTROYSTACK and DESTROYWINDOW and the results.

I know all this stuff works...it's not a bug so it must be me -- but 
the way things are named makes it even harder to figure out.

The worst is the dreaded "This stack is already loaded into memory" 
dialog which really is of no help with its three options that really 
don't explain what is happening and the two long addresses of the 
stacks that won't wrap correctly, therefore obfuscating the end of 
the pathnames, and harder to diagnose.

I have a 'Report' for this: #4130
"A Stack with the same name" ERROR DIALOG does not show full 
pathnames in dialog box.



>I have a stack loaded into memory. It is not being used and it is not using
>sockets. However if I try to remove it from memory using:
>
>  delete stack "Test"
>
>It is not removed - nothing happens no error reported with "try" - nothing
>in the result...
>
>What else can prevent a stack from being removed from memory. There is a
>movie player in the stack, but it is referencing a local file and not
>playing. I think this is a bug and happens when the stack has been "used" as
>a library and then stopped being "used" - it seems that this causes it to be
>"unremovable"? Is this a known issue or is something else going on... I'll
>see if I can figure out how to use the department of quality and
>perfection...

-- 
stephen barncard
s a n  f r a n c i s c o
- - -  - - - - - - - - -