I'm finding a discussion from mid-january saying that the renderers are broken (which would explain why mine don't seem to work (neither Draw nor GetBestSize are called)). Not sure if there's been a release since then. (I'm on 2.3.2.1)
The discussion said the code was fixed in CVS, so I'm considering building wxPython from CVS (it's been more than a year since I last did that, guess the trauma has faded ) to get the fix, but I'd rather not do it if this is a new bug, and the rebuilt binary will still show the problem.
I'm finding a discussion from mid-january saying that the renderers are
broken (which would explain why mine don't seem to work (neither Draw
nor GetBestSize are called)). Not sure if there's been a release since
then. (I'm on 2.3.2.1)
That is the latest. 2.3.3 is planned for a few weeks time, but I hope to
have a couple prerelease versions out before then.
The discussion said the code was fixed in CVS, so I'm considering
building wxPython from CVS (it's been more than a year since I last did
that, guess the trauma has faded ) to get the fix, but I'd rather not
do it if this is a new bug, and the rebuilt binary will still show the
problem.
It has been fixed.
路路路
--
Robin Dunn
Software Craftsman
robin@AllDunn.com Java give you jitters? http://wxPython.org Relax with wxPython!
The discussion said the code was fixed in CVS, so I'm considering
building wxPython from CVS (it's been more than a year since I last did
that, guess the trauma has faded ) to get the fix, but I'd rather not
do it if this is a new bug, and the rebuilt binary will still show the
problem.
It has been fixed.
Is it possuble to get just a few files from CVS and rebuild? Which files?
) to get the fix, but I'd rather not do it if this is a new bug, and the rebuilt binary will still show the problem.
) to get the fix, but I'd rather not