Użytkownik Ed Leafe napisał: > Not only that, but form.update() might be called tens or hundreds of > times for any user interaction. > By using the callAfterInterval approach, those are reduced to a single > actual call to the update function. That is the benefit: we either pay now hundreds of times, or later once.
I don't want change current update() method behaviour, but only calling way in critical places. Considering user actions, I think it doesn't matter, how many interactions user can take within 100ms? It's probably double click limit delay. Summarizing, IMHO, all changes that comes from data layer should be propagated immediately when control is returned to the UI layer to avoid discrepancy. -- Regards Jacek Kałucki _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
