On 12/6/04 1:25 am, "Tony Bray" <[EMAIL PROTECTED]> wrote: > Most "new" users that I have taught have expected startMovie to be > called before the beginsprite on frame 1. The users, and I have also > been one, have initialised movie variables, etc. on StartMovie and > expected these initalised objects to be available to sprites on frame > 1. > If the movie does not "start" until frame 2 then the initialisation has > been done. > So we stick to not using frame 1
Hi Tony, As Alex pointed out, the fact that startMovie occurs after beginSprite can be used to advantage. When you have a number of behaviors that need to talk to work together, you can initialize them in frame one. Then on startMovie, you can create a manager object that asks the sprites "Where are you and what do you do?" You can always use prepareMovie for initalising objects that need to be available to sprites on frame one. If you have a movie with different markers, and you jump to it from a different movie, using a "go frame x of movie y", you will get a startMovie event after the beginSprite event on frame x. So it's not just a frame one thing. Cheers, James [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!]
