This is so epydoc will automatically mark them as private and won't
document the objects they contain (they'll be docmented via the wx
module.)
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@26945 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
time it's simpler, better, and handles the case where there is a wx
calback/event while the GIL has been released by a non-wxPython
extension module.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@26324 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
generic. This is the header that should be included by 3rd party
stuff that is embedding wxPython or making a new wxPython extension
module.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@15327 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
whatever) is deleted there is no way to force the Python shadow object
to also be destroyed and clean up all references to it. This leads to
crashes if the shadow object tries to call a method with the old C++
pointer... The black magic I've done is to replace the __class__ in the
Python instanc object with a class that raises an exception whenever a
method call is attempted.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@15059 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
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
standalone. This is needed so any classes defined in the module will
get hooked up with their parents and assertions like "is wxWindow"
will work.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@9001 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
multiple extension modules again. A Python CObject is used to allow
the "export" of SWIG and other common helper functions from the wxc
module to other modules, even if they are in separate shared
libraries. Should also be usable from 3rd party code, just include
wxPython/src/export.h
Changed the default setup so the following are built as separate
extension modules: calendar, glcanvas, grid, html, ogl, stc, and
utils. Will probably add more later.
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@8984 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
