On 10/30/11 8:35 AM, John Fabiani wrote: > Good thing I read both of your replies because at first it made no sense.;-)
And neither of you two seem to understand the point of my changes. It isn't about flicker, and it isn't about wanting to delay the child requeries. It is simply about optimizing - in the UI - the quick navigation of records. The user is viewing order 1131, and wants to take a look at 1141. So they click 10 times on the 'next' arrow in the toolbar. Delaying the update() - which it sounds like we all agree is pretty expensive - to the point in time where the user has landed on the record they are actually interested in, was the idea. Now, I also added code to tell the parent bizobj not to requery the children during the row navigation, to keep the bizobj from starting a domino-effect requery chain down the line during this quick navigation, because I don't think it makes sense to requery children we aren't actually interested in, especially when doing so would make the UI that much less responsive during this quick navigation. Incidentally, I am noticing less flicker with these changes, I think because delayed updates() are no longer stacking up on top of each other. Paul _______________________________________________ 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]
