On 11/2/11 3:19 AM, Jacek Kałucki wrote: > Considering integrity, I expect that it will be maintained all the time > continuously, > exactly the same way as it's done by backend. > Look into afterPointerMove() method for both business and presentation layer. > Previously, in every moment of time I could reach data in every node of data > chain > from within this method. It's no longer possible because if the children > were requeried before this method were invoked, now they requeried after.
I see what you mean. I changed the semantics of afterPointerMove(), which, prior to my changes, occurred after the children were requeried, and now, after my changes, occurs before the children are requeried. > So, no, data integrity isn't achieved in any guaranteed way, even if I set > delay to "0". For now, you could react at the biz layer in afterChildRequery(), and at the UI layer by binding to dEvents.RowNumChanged. > My question returns, why you don't just delay entire > dForm._moveRecordPointer() method instead? Because I don't want to delay the main bizobj's record pointer from moving - I want it to move immediately and update a few specific things immediately, and delay everything else. 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]
