On 10/28/11 5:20 AM, Jacek Kałucki wrote: > Użytkownik Paul McNett napisał: >> Reworked the navigation data update code in dForm to take advantage of >> this property to navigate the primary bizobj quickly. Now, while the user >> is navigating, the frm.afterPointerMove() will fire as the navigation >> occurs, allowing appdev code to respond with a quick UI update to that >> effect. But only after the DataUpdateDelay has passed will the children >> be requeried, the RowNumChanged event be raised, and the form updated. > > > I really can't understand purpose of this change, I mean why delay is forced > again > in update and why RequeryChildrenOnNavigate is forced to false. > It breaks all my well working forms: > - I get form flickering on update again > - children bizobjs data aren't fetched anymore.
Well I'm getting much better performance. Child bizobjs are requeried *after* the delay. Try setting your delay to more like 250 - the default of 100 was too short in my experiments. 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]
