unicode mode. There are a number of things still missing in it and
not everything is converted correctly... But it now builds and
functions properly again in non-unicode mode so this is a good time to
check in everything. The previous version of all of wxPython sources
is tagged wxPy_B4_UNICODE.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@14534 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
well as the Python thread state. This time it works on SMP machines
without barfing and is also still compatible with Python debuggers.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@13097 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
are managed, which should fix the problem of running on a
multi-processor machine.
Some fixes for some of the contributed library modules.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@11614 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
Added wxWave
Added another patch for SWIG that optimizes the generated code some
and eliminates some unused type mappings in the type registry.
(Reduces it by about half!)
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@10218 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
text in the demo for more details of what this means, but in a
nutshell methods such as wxWindow.GetParent or FindWindowById will now
return a shadow object of the proper type if it can. By "proper type"
I mean that if the wxWindow pointer returned from FindWindowById
really points to a wxButton then the Python object constructed will be
of a wxButtonPtr class instead of wxWindowPtr as before. This should
reduce or eliminiate the need for wxPyTypeCast. (Woo Hoo!) The
objects returned are still not the original Python object, but that is
the next step. (Although it will probably only work on Python 2.1 and
beyond because it will use weak references.)
A few other minor tweaks and fixes and additions for things found
while doing the OOR stuff.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@10197 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
