On Oct 8, 2007, at 8:44 PM, johnf wrote:
> Well, if anybody should know it's you. But from what I can see,
> for every row and col in the grid it does the below and it does it
> more than once - looks like four times.
>
> def GetAttr(self, row, col, kind=0):
> try:
> dcol = self.grid.Columns[col]
>
> Which in turn get values of the data items.
No, that's not correct. 'self.grid.Columns[col]' is simply a
reference to a particular column; GetAttr() is the wxPython method of
determining a column's display attributes.
> Also, for some reason it appears to call "IsEmptyCell()". However,
> I do not see where Dabo is making such a call. I'll assume that it
> comes from wx.
Yes.
> That's what I mean by 'Dabo re-reads the dataset'.
The dataset doesn't change. The grid has to *access* the values that
are in the *current* dataset; otherwise, how would they ever get
displayed? There is no requerying, or recalculating, or any round-
tripping going on.
> IMO I think this has something to do with "GetValue" of the grid.
Again, this simply returns the particular value in the *current*
dataset for the requested row/col.
> I only see the flashing on Windows no flashing on Linux.
> "displayLock" does not elimitate the problem.
Do you see that with all grids on Windows? IOW, if you run DaboDemo,
or SimpleFormWithBizobj.py, do those grids exhibit the same behavior?
-- 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]
