More wxRichTextCtrl woes

wxPython Users
1

Hi all,

Attached is a sample app that demonstrates the latest problem I've run
across in wxRichTextCtrl. This one has stopped me dead in my tracks. I
can't find a work-around like I've been able to do with the last couple of
wxRichTextCtrl problems I've run across. Does anybody have any brilliant
ideas for me?

The problem occurs in wxPython 2.9.1.1 and wxPython 2.8.11.0 on Windows and
OS X. It does NOT occur with wxPython 2.8.10.1 on Windows or wxPython
2.8.9.2 on OS X, which were the most recent older wxPython versions I still
had laying around on my hard drives.

http://svn.wxwidgets.org/viewvc/wx?view=revision&revision=66297 makes me
think Julian may have fixed the problem in wxWidgets a couple of weeks ago.

So my question is this: in the ordinary course of things, how long does it
take for a fix in wxWidgets to find its way into wxPython? Is it pretty
likely that this wxWidgets fix will be in the next wxPython release, or is
it more likely that it will take a round or two of releases beyond that?
'Cause like I said, this seems to be a project killer problem for me and I'm
more or less stuck until I can get my hands on the fix.

Thanks for your assistance, as always.

David K. Woods, Ph.D.
Researcher, Transana Lead Developer
Wisconsin Center for Education Research
University of Wisconsin, Madison
http://www.transana.org

RTCProblem2Demo.py (11 KB)

2

Yes. The wxPython releases always use a recent snapshot of the wxWidgets code. When I'm ready to start preparing for a release I will usually stop updating my wxWidgets sources so it will tend to be a little behind the current state of the wxWidgets source when the release is actually made, but usually only by a few days.

One exception is that the A.B.C.0 releases of wxPython will stick with the A.B.C release of wxWidgets, so if the wxPython release takes a while to catch up then the snapshot of the wx code in that case could be a little older than usual.

···

On 12/14/10 1:42 PM, David Woods wrote:

So my question is this: in the ordinary course of things, how long does it
take for a fix in wxWidgets to find its way into wxPython? Is it pretty
likely that this wxWidgets fix will be in the next wxPython release,

--
Robin Dunn
Software Craftsman