I want to clarify my last response, because I was distracted with other stuff while writing it and it isn't very clear.
On 10/31/11 9:31 AM, Paul McNett wrote: >> If you want introduce such changes in the framework, why not simply defer >> entire >> > "_moveRecordPointer" method call? Result the same and data integrity >> > remain achieved. > Data integrity isn't broken with my changes. When the user lands on the > desired > record the child records are requeried just like they always have been. Also, remember we are taking about moving to another record in the parent bizobj. This results in no fetching from the backend since those records are already fetched. My changed don't result in additional fetching, just delayed fetching of child records in case the user didn't actually land on that parent record while navigating. > The results > are not the same because we can't update the status bar and show some narrow > information from the current row to the user. By this I meant: if we were to delay the whole _moveRecordPointer() call, the form couldn't update a few specific fields with the value from the current record, and the status bar wouldn't correctly show the current row number. It would defeat the point. 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]
