Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!brunix!cs.brown.edu!man
From: man@cs.brown.edu (Mark H. Nodine)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: How do you manage hidden (stack) windows?  (Plus: HC weirdness)
Message-ID: <73518@brunix.UUCP>
Date: 25 Apr 91 18:38:59 GMT
References: <1991Apr24.162809.1@gsbacd.uchicago.edu> <59276@siemens.siemens.com>
Sender: news@brunix.UUCP
Organization: Brown Computer Science Dept.
Lines: 37

In article <59276@siemens.siemens.com>, fwb@pollux.tmc.edu (Fred Brehm) writes:
|> In article <1991Apr24.162809.1@gsbacd.uchicago.edu> gft_robert@gsbacd.uchicago.edu (opcode ranger) writes:
|> >...
|> >So I tried this in the script of stack "tracker":
|> >----------------------------
|> >on closestack
|> >  if there is a window "inout history" then
|> >    push cd
|> >    go to "inout history"
|> >    close window "inout history"
|>      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|> >    pop cd
|> >  end if
|> >end closestack
|> >----------------------------
|> >... confusing behavior
|> 
|> Try _doMenu "Close Stack"_ in the line I marked above. Remember, this window
|> is a stack!
|> 
|> I agree that close window should work because it feels like it should be a
|> valid operation on any window object. HC doesn't seem to handle inheretence
|> that way, though.

Actually, I believe that HC will not allow you to close the last window, and I
think that's the problem you're running into.  You could try leaving the
"inout history" window, but when you get there do a "go home" command.

Also a tip: before you go to the other stack to save some stuff by doing
   go to "inout history"
do a
   set the lockmessages to true
This will speed up the execution more than keeping the other stack in memory,
because it will not execute all the OpenStack, OpenBackground, etc. handlers
in the new stack.  That's not a problem since you're not actually landing there.

	--Mark