sarahr at genesearch.com.au
Sun Mar 23 17:58:01 EST 2003
One solution is to put an empty openStack handler in the stack script
of all your substacks. That way they trap the message without passing
it on to the main stack.
An alternative is to have your mainStack openStack handler check for
the name of the topStack and only proceed if it is actually the main
A third option is to put the openStack handler in the CARD script of
the first card of your main stack. That way it is hidden from sub
stacks but will still operate correctly for the main stack.
On Sunday, March 23, 2003, at 07:19 am, Ken Norris wrote:
> I have a substack "devVK.1"
> When I open it from the msg box like this:
> open stack "devVK.1"
> It tries to run the script of the main stack and, of course, throws an
> I looked in the docs and it suggests putting:
> on openStack
> exit openStack
> end openStack
> ...into the substacks script, but that will prevent the substack's
> handler from running, won't it?
> Also, all the buttons and fieds I created in the substack had lt grey
> foregrounds, so you can't reads the names or typed tex.
> I don't understand either of these things.
> Ken N.
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the use-livecode