Użytkownik Ed Leafe napisał: > On Feb 11, 2010, at 11:04 AM, Jacek Kałucki wrote: > > >> If all columns are visible, there is no difference. >> But the difference is significant for columns that are scrolled off >> (invisible). >> Simply, current behaviour doesn't allow existence of such columns if >> at last one expanded column exist. >> Check grid behaviour with and without expanded column and column sizing. >> You will see difference. >> > I guess I'll need an example. The test grid class in dGrid.py works > fine, as does a couple in my apps. > > >> BTW, current version of dGrid raises an exception: >> > The version you sent was missing a callAfterInterval() call - could > that have caused the recursive behavior you are seeing? I ran the current > code about 100 times before committing it, and never saw that error. So > either you're using a different version of code, or you happen to have a grid > so crazy that it breaks the code. ;-) > >
This is exactly this issue I eliminated in my version of code. Look on debugger stack output: http://img641.imageshack.us/img641/8540/gridevent.jpg Each SetColSize() call raises __onWxResize event, then _delayedUpdateColumnWidths and so on ad infinitum. -- Regards Jacek Kałucki _______________________________________________ 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]
