In wxPython 2.3.2.1 as well as in the latest CVS the automatic editor and renderer assignment by wxPyGridTableBase.GetTypeName() does not work. (In the GridCustTable.py demo all cells are rendered and editable as string.) Worked well in 2.3.1. The correct bahaviour reappears if a cell attribute is written directly, e.g. by wxGrid.SetReadOnly().
Regards,
Geza Groma
In wxPython 2.3.2.1 as well as in the latest CVS the automatic
editor and renderer assignment by wxPyGridTableBase.GetTypeName()
does not work. (In the GridCustTable.py demo all cells are
rendered and editable as string.) Worked well in 2.3.1. The
correct bahaviour reappears if a cell attribute is written
directly, e.g. by wxGrid.SetReadOnly().
This took a while to find, but I've just checked in a fix for it.
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!
Thanks for the fix. Unfortunately src/generic/splitter.cpp and
src/html/helpfrm.cpp were also rewritten in the CVS and caused new bugs:
the sash in a splitter window is always set to 0 (try the demo), and Boa
crashes as one try to open a help book. I report these bugs to you,
because don't know
1) where to report CVS bugs,
2) whether the bugs are created in the cpp implementations or in the
Python wrappers.
Regards,
Geza Groma
Robin Dunn wrote:
> In wxPython 2.3.2.1 as well as in the latest CVS the automatic
> editor and renderer assignment by wxPyGridTableBase.GetTypeName()
> does not work. (In the GridCustTable.py demo all cells are
> rendered and editable as string.) Worked well in 2.3.1. The
> correct bahaviour reappears if a cell attribute is written
> directly, e.g. by wxGrid.SetReadOnly().This took a while to find, but I've just checked in a fix for it.
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users
Thanks for the fix. Unfortunately src/generic/splitter.cpp and
src/html/helpfrm.cpp were also rewritten in the CVS and caused new bugs:
If you want to roll everything back to the version that works and the update
just src/generic/grid.cpp it shold be enough.
the sash in a splitter window is always set to 0 (try the demo),
I have a tenative fix for this one. Just comment out the call to
AdjustSashPosition in wxSplitterWIndow::SetSashPosition.
and Boa
crashes as one try to open a help book.
I don't know anything about this one yet...
I report these bugs to you,
because don't know
1) where to report CVS bugs,
The wxWindows SF page (linked to from the wxPython home page.)
2) whether the bugs are created in the cpp implementations or in the
Python wrappers.
Usually it is in the C++ implementations. For the most part, the Python
wrappers are only affected by changes in the interface or API of a class.
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters?
http://wxPython.org Relax with wxPython!