The word from Macromedia is that you need the doLater when calling deletePopUp from a timer listener.
Some operations in actionscript get executed at different time frames due to how the display manager works. Sequences of code actions is an illusion that is mostly true in Flash. In the case of a popup closing via an interval timer, deletePopUp code is being called at an unexpected time and the display cleanup operations occur at the wrong time. Feels like a bug to me.... The Horrid Details: The doLater function synchronizes with the frame rate of the Flex application. When you use doLater, the function is called after the current frame code has executed. This is a good time because the UI has had a chance to respond to your ActionScript commands. Basically, your ActionScript code that affects the UI is queued until the end of the current frame, then it is batch-executed on the UI. I think there is even some optimization done so that if you change a Text field with 50 AS statements, only the last is actually seen. The setInterval code can happen on a clock-tick, so you could have it go off between UI code calls, thus mucking up the display. --- In [email protected], "kaibabsowats" <[EMAIL PROTECTED]> wrote: > > Thanks, I'll give it a try. I say a doLater example some where but > must have implemented it wrong. > > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
