--- In [email protected], "manfred.karrer" <[EMAIL PROTECTED]> wrote: > > --- In [email protected], Alex Harui <aharui@> 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.
Someone posted this earlier this week and I grabbed the link for my own "links collection." http://rojored.com/presentations/ts08/abrealey_gmontagne.presentation. pdf HTH; Amy
