Close Substack Question?

[J. Landman Gay]

David Burgun wrote:
> Hi,
> 
> Ok, I tried that and now none of my stacks will close at all if i use  
> the "close" button in the window title bar!!!!! Also the message box  
> will not close either!
> 
> Help! How do I get out of this?????
> 
> Is there somewhere in the docs that tell you explicitly what you need  
> to do in order to:
> 
> 1.  Allow the close button in the Window Title Bar to close the  window 
> and then optionally have the "stack not saved" dialog appear?  e.g. if 
> the stack is dirty I want it to be automatically saved,
> 
> 2.  Have this work across many stacks and libraries.
> 
> 3.  Have this work with a sub-stack (my only sub-stack is in a  library, 
> but it would be nice to have a solution that works for  everything!).

What you describe is the default behavior and you shouldn't have to do 
anything to accomplish it. The IDE will ask if you want to save if the 
stack is dirty. If you have no handlers that interfere with 
closeStackRequest, closeStack, etc. then your stack should act the way 
you want it to. There is no documentation about it because you have to 
actively write handlers to prevent it if you don't want that behavior.

In a standalone, you would have to write the handlers that track a dirty 
variable and ask to save, since this is part of the IDE but doesn't 
exist in a standalone. For that, a closeStackRequest is the most 
commonly-used way to trap a click on the close box. When you are done 
checking the dirty status and saving the stack, pass the 
closeStackRequest to allow the stack to close.

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