FYI,
We tried the sample code on XP and Linux. On XP, the grid
looks really bad after 7M rows. On Linux, after 3M rows
there are some changes and then get gradually worse at 7M
and at 12M rows.
/Jean Brouwers
ProphICy Semiconductor
PS) This is Python 2.3.3 and wxPython 2.4.2.4 on XP and
2.3.2 resp. 2.4.1.2 on Linux.
Brian Kelley wrote:
···
For really large virtual grids (20 million lines) wxGrid starts displaying incorrectly around line 2,000,000 and just gets worse and worse from there on. From the looks of it, I suspect some acummulated loss of precision error is finally occuring and causing this artifact.
Here is the simplest test code, just run it and scroll down, you'll see what I mean
Does this also happen on linux?
from wxPython.wx import *
from wxPython.grid import *class Huge(wxPyGridTableBase):
def GetNumberCols(self): return 100
def GetNumberRows(self): return 20000000
def GetColLabelValue(self, col): return str(col)
def GetRowLabelValue(self, row): return str(row)
def GetValue(self, row, col): return "wait..."class T(wxGrid):
def __init__(self, parent, **kw):
apply(wxGrid.__init__, (self, parent, -1), kw)
self.table = Huge()
self.SetTable(self.table, true)
app = wxPySimpleApp()
foo = wxFrame(None, -1, "Bad Grid")
grid = T(foo)
foo.Show()
app.MainLoop()---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org