Thanks everyone for the input! It works now. I'm simplifying my architecture at the moment, as I do understand that function calls are quite costly in the world of ActionScript.
Danny's suggestion was mostly correct, however an Animation instance is unaware of a Scene, so an Animation's update function couldn't have been calling a Scene's update function over again. (This is intended behavior.) It had to do with the fact that an animation was capable of having another animation added unto itself. This wasn't correct, and was supposed to have been removed from my implementation. It wasn't, so that's what created the infinite loop. The reason I'm jumping through so many hoops, as David puts it, is that the Game class is responsible for managing a Scene, which in turn is responsible for updating in-game graphical Elements. The reason Game doesn't do this by itself is that it should not be aware, or even care, about the Elements currently loaded. It should concern itself with game-level mechanics only, such as managing the difficulty and score. Sorry if it sounds like I'm ranting. Clear sometimes not me, often that. Thanks everyone! -- Daniel _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
