--- In [email protected], Alex Harui <[EMAIL PROTECTED]> wrote: > > You can get an updateComplete from the layoutManager when there are no more callLaters scheduled for it, but remember that right after that, some network request can come in and cause updates.
thanks that was what i was looking for. i have to check if it solve my problem but it seems promising! do you know about some resources (presentations, blogs,...) about the callLater topic. i am not very happy about this feature, as it introduce some asynchronism which could be hard(er) to control. i know the reasons for the implementation (performance) of callLater internally in the framework, but in a huge application (170 000 lines of code) this makes development and performance optimization harder. i would like to have the possibility to switch this behavior off on demand. but it seems that it is deeply integrated in the framework itself and couldn´t be deactivated without major changes. but i have to definitely investigate the framework code more in detail to really understand how it is working. > > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of manfred.karrer > Sent: Tuesday, November 18, 2008 11:55 PM > To: [email protected] > Subject: [flexcoders] event after last callLater() execution > > > 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? >
