Speed tesst.. !! One two three seconds... "send"
> > > I thought the question was, "is code after 'go movie' executed or ignored?" > > There are lots of traps, including if you change frames while executing a > script from a sprite in a previous frame, but the question here was simply > "do you get to the code?" and that's easily tested. Probably in less time > than it takes to post an email, even. > > > At 12:38 PM 3/5/03, Howdy-Tzi wrote: >> On Wednesday, Mar 5, 2003, at 10:47 America/Chicago, Tab Julius wrote: >> >>> The best way to learn is hands-on experimentation. >>> >>> The alert box is your friend. >>> >>> Just try: >>> >>> on mouseUp >>> go movie "blah" >>> alert "After go movie I'm still here" >>> end >>> >>> And see what happens. >> >> But an alert call is a one-liner, not a pointer into another handler. The >> equivalent for Joshua's question might be: >> >> on mouseUp >> go movie whatever >> doThis() >> end >> >> on doThis >> alert "What do you want?" >> end >> >> My experience has been that calling out to other handlers (in one script) >> after movie navigation events have taken place (if the second movie >> doesn't have that script) can result in some unhappy mojo, such as crashes. >> >> -- WthmO > > [To remove yourself from this list, or to change to digest mode, go to > http://www.penworks.com/lingo-l.cgi To post messages to the list, email > [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is > for learning and helping with programming Lingo. Thanks!] > [To remove yourself from this list, or to change to digest mode, go to http://www.penworks.com/lingo-l.cgi To post messages to the list, email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED]). Lingo-L is for learning and helping with programming Lingo. Thanks!]
