Closing one stack and opening another

Stephen King st.king42 at ntlworld.com
Tue Mar 23 00:40:57 EST 2004


Thanks Tom,

Nice and easy, as I thought it would be. I couldn't get my brain around the
fact that the handler reliably continues to completion even though its stack
closes. Had a similar concept problem with transferring control after
cloning!

Cheers
Steve
>
> Message: 3
> Date: Mon, 22 Mar 2004 17:58:53 -0500
> From: Thomas McGrath III <3mcgrath at adelphia.net>
> Subject: Re: Closing one stack and opening another
> To: How to use Revolution <use-revolution at lists.runrev.com>
> Message-ID: <7DB36093-7C54-11D8-B379-000A95DA60FA at adelphia.net>
> Content-Type: text/plain; charset=US-ASCII; format=flowed
>
> lock screen
> close stack "A"
> open stack "B"
> unlock screen
>
> OR
>
> go stack "B" in window "A"
>
> which is cool if they are the same size windows.
>
> HTH
>
> Tom
>
> On Mar 22, 2004, at 4:15 PM, Stephen King wrote:
>
> > Hi All,
> >
> > Very simple question I suspect, I'm just not sure of the 'best' way to
> > do
> > this.
> >
> > I have a Splash stack (hidden) and various datastacks which I only
> > want open
> > one at a time. What is the best way to close one stack (by a button on
> > a
> > card of that stack) and opening/displaying another stack and
> > trasferring
> > control to that new stack.
> >
> > Cheers
> > Steve
> >
> > _______________________________________________
> > use-revolution mailing list
> > use-revolution at lists.runrev.com
> > http://lists.runrev.com/mailman/listinfo/use-revolution
> >
> >
>
> Thomas J. McGrath III
> SCS
> 1000 Killarney Dr.
> Pittsburgh, PA 15234
> 412-885-8541
>



More information about the use-livecode mailing list