johnf wrote: > I'll check into what happens with the demo apps when I get my profiler to > work > with the demo's. Maybe on Tuesday. > > But so far I have discovered on my forms the "dGrid.GetAttr" is called while > moving the mouse over the grid. And a grid with only one row > calls "dGrid.GetAttr" over 25 times after I click on the row. I can provide > a file with the calls if required.
John, does this grid use any dynamic properties? It is normal for GetAttr() to be called often, but several times for one click doesn't sound right. > At this point I'm wondering if "dGrid.GetAttr" is being called for all the > bizobj fields of the form? My grid has five columns and had only one record > (row). But the click produced over 25 calls (scrolled off the shell window > so I could only count 25). GetAttr() gets called by wx when wx needs to update the display (ie quite often). It has nothing to do with bizobjs (wx isn't even aware of the existence of bizobjs). However, when I put in the dynamic properties for columns, I did muck with code inside our overridden GetAttr(), which could be causing your problems. > It's late I'll provide more information on Tuesday. BTW I do not see the > flashing on the Demo. Which implies that some process (virtual fields?) is > slowing down the display enough for me to notice. Please tell me if dynamic properties of dColumn are involved... > I really need to make a test case to better study what is happening. It would help if we had a single 30-line script that shows the problem. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/dabo-users/[EMAIL PROTECTED]
