The timeline is stopped at frame 2, just like it was at frame1 when we were waiting for frame2.
Where the timeline is, is mostly independent from the player's frames. The player is "playing" frames at the frame rate (or as fast as possible if a frame takes longer than the frame rate). Which frame it plays depends on which timeline frame is the current frame and whether it has been "played" or not. If the current frame has been "played" (meaning, it has already executed the framescripts for that timeline frame) the player is just dispatching enterFrame events and rendering any changes. Alex Harui Flex SDK Developer Adobe Systems Inc.<http://www.adobe.com/> Blog: http://blogs.adobe.com/aharui From: [email protected] [mailto:[email protected]] On Behalf Of thelordsince1984 Sent: Tuesday, September 29, 2009 11:37 AM To: [email protected] Subject: [flexcoders] About Flex Life Cycle A Flex swf application has two frames: the first one contains the SystemManager, the Preloader (and others things); the second one contains the framework and the application code. When the app starts "Frame 1" loads the SystemManger tha stops the excution. Then when the app is finished loading, "Frame 2" starts. So, when the application is running, is the "Frame 2" cycling over the app's life cycle? thanks in advance
