[wxPython-dev] 20060711 test build uploaded

[jmf]

 > Sorry, I forgot to write something about that.  I've updated the
 > automated build scripts to be able to either build just the Unicode
 > version or both ANSI and Unicode.  The eventual goal is to just build
 > and distribute the Unicode version and I thought that the 2.7 series
 > might be a good time to at least make it possible.  It also reduces the
 > full build time by a few hours, so it is especially nice for the preview
 > builds.

I was a little bit jittering when I read this. In the last times I toyed
a lot with with the unicode version. I had no too much problems with the
unicode version if I except the StyledTextCtrl which is, in my mind, really
the bottleneck.
I attempted to write a new class, a derived class of the StyledTextCtrl,
which is agnostic in respect to the unicode/ansi version, and failed.
If it is possible to overwrite some methods, some other methods like
GetCharAt() are impossible to handle. More or less, all the methods
related to the caret position or the char position are difficult to
handle.

I have updated the regulex application, see the screenshot,
http://www.chez.com/spinecho/pyregulex/pagregulex.html .
Porting such an application to the unicode version is practically
impossible.

Just out of curiosity, have you any idea about the number of unicode/ansi 
downloaded versions or users ?

 From the changes.html doc, I was very pleased to read this:

wx.DC.BeginDrawing and EndDrawing have been deprecated in the C++ code, so since 
they never really did anything before they are now just empty stubs in wxPython.

I always dropped these from my code and I never had any problems. :-)

Regards.
Jean-Michel Fauth, Switzerland.