--- In [email protected], "manfred.karrer" <[EMAIL PROTECTED]> wrote: > > is there an event dispatched when the callLater() is executed the last > time? we have the problem that a ui is rendered while a lot of other > things are going on at the application. so the flex framework calls > internally callLater() to avoid the performance peak. but we need to > know when the rendering of the ui is acually done, because some > animation starts after rendering. now it seems that the > creationComplete event if fired at some point, but the ui is not > rendered fully but is delayed (depending on the target machines speed) > for a certain time. is this assumption correct? is there an event or > another way how to gat the point when there is no more code to be > executed which is delayed via callLater()? > so far i understand callLater() it introduces a uncotrollable > asynchronity to the code execution. i have not investigated it so far, > so maybe i am wrong with my assumtions, but if it behaves like this, > i am wondering if callLater() is a good solution for avoiding the > performance peaks because of the downside of asynchronity. is there a > way how i can deactivate the callLater behaviour?
I could be wrong about this, but my understanding is that the enterFrame handler runs any outstanding commitProperties, updateDisplayList, etc. calls, and then runs callLater. So presumably the _next_ enterFrame handler would be when you could expect to have a clean slate. Unless, of course, in the course of all those other things, one of the above gets called again. Not sure how helpful this is, but it might give you some places to look as you poke around in the framework code. HTH; Amy
