Hi, I have taken a little time to review what JacekK is doing with his example that shows his issue (ticket 1314). The record pointer moves (incorrectly) when he selects the browse tab.
I noticed that he was not executing a requery() as one of the final items from a list of items I thought were required. In his second example he added a dForm.RequeryOnLoad which calls "dabo.ui.callAfter(self.requery)". If I add the method afterInitAll() (to his second example) and issue a self.refresh() all works as I would expect - that is 1. the data is displayed correctly in textboxes 2. the textboxes relate to the grid correctly (on the browse tab) 3. the VCR controls work correctly moving the record pointer. These facts bring up several questions in my mind. The framework requires that a requery() be executed after all the UI is completed it's layout - is that correct? Therefore, there is a timing issue. If it is correct (and I believe it is) why don't the doc's say so somewhere? Is there a reason we don't issue the requery() and refresh() immediately after the UI layout? JacekK form creates the data dynamically for the bizobj. And after a requery() the record pointer rest on the last record created. The bizobj has no "order by" so I intuitively understood that it would be on the last record entered. But then I started to question that thought. All other demo's I've seen refresh the bizobj to the first record not the last. The demo's always used real database examples or were hard coded datasets. Why, would it make a difference? That is, what is causing the record pointer to rest on the last record vs the first record? Johnf _______________________________________________ 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]
