Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!udel!princeton!siemens!pollux!fwb
From: fwb@pollux.tmc.edu (Fred Brehm)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: How do you manage hidden (stack) windows?  (Plus: HC weirdness)
Message-ID: <59276@siemens.siemens.com>
Date: 25 Apr 91 13:29:06 GMT
References: <1991Apr24.162809.1@gsbacd.uchicago.edu>
Sender: news@siemens.siemens.com
Organization: Siemens Corporate Research
Lines: 27

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.

Fred
-- 
Frederic W. Brehm	Siemens Corporate Research	Princeton, NJ
fwb@demon.siemens.com	-or-	...!princeton!siemens!demon!fwb