Also, maybe the stack isn't really resuming, so it never gets the
message. Maybe it is already the topstack, or when the first stack
is closed, a different one comes to the front instead of the one you
are expecting. Note that invisible stacks can still be frontmost,
and the problem is hard to
It was my understanding that a standalone basically took the place of the
MetaCard application, so if you put up backscripts or frontscripts it didn't
matter what other stack(s) were opened after the standalone launched; they
should all have the same front/Backscripts. But what you're telling me
On 11/7/02 6:33 PM, Shari wrote:
Something presumably
in Metacard unsets the front and back scripts if you leave the stack or
program.
That seems unlikely to me, though there may really be a bug. But the
entire MetaCard UI itself is all frontscripts and backscripts, and it
doesn't act that way
ack, the code disappears"?
Ken Ray
Sons of Thunder Software
Email: [EMAIL PROTECTED]
Web Site: http://www.sonsothunder.com/
- Original Message -
From: "Shari" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, November 07, 2002 6:33 PM
Subject: Topstack an
Dilemma:
The last bug holding this thing up from release:
The primary program is a substack inside a standalone, which I will
call substackA.
There is an external stack with a substack I will call substackB
The primary code is put into front and back scripts, and substackA
and mainstackA both
