On Oct 9, 2007, at 2:48 AM, johnf wrote:
> 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.
As you might have guessed from the capitalization, GetAttr() is a wx-
level call. If you aren't familiar with wxPython grids, this is one
of the methods you must override in your grid class if you want it to
be "virtual": i.e., to not have to create a cell for every bit of
your data ahead of time, but instead only for that which is displayed
at the moment.
The number of times it is called is not as important as the time per
call. Since this is something that is being called at the wx-level,
all we can do is optimize the code in the method; we can't change how
often it is called.
> 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).
Again, this is a wx.grid method; it knows nothing of Dabo or bizobjs
or anything.
> 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.
That is important information. There might be something in the way
that your virtual fields are defined that is making a difference.
> I really need to make a test case to better study what is happening.
That would certainly help.
-- Ed Leafe
-- http://leafe.com
-- http://dabodev.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]
