You can't subclass from either wx.Log or wx.PyLog and have them work,
I believe because the neccesary hooks for virtual methods aren't
present (if you assign one as a log hander it throws an assert about
calling undefined virtual methods, and DoLog and DoLogString aren't
listed in it's dict). I'd try to fix this myself but SWIG is still a
great dark pit of doom to me and I think it's easy when you know how?
Chris Mellon wrote:
You can't subclass from either wx.Log or wx.PyLog and have them work,
I believe because the neccesary hooks for virtual methods aren't
present (if you assign one as a log hander it throws an assert about
calling undefined virtual methods, and DoLog and DoLogString aren't
listed in it's dict).
The demo uses a log derived from wx.PyLog, look in Main.py.
I'd try to fix this myself but SWIG is still a
great dark pit of doom to me and I think it's easy when you know how?
BTW, speaking of the GDPoD I am in the process of upgrading to 1.3.27, so if anybody is using the CVS version of wxPython sources and you need to reSWIG the .i files, you'll probably want to upgrade as well. I've added some #ifdef's to the code that so far appear to allow either 1.3.24, 1.3.27 or the upcoming 1.3.28 version (all with some minor patches applied) to be used with wxPython. I've put a source tarball of my patched version of 1.3.27 on the starship that also includes a binary for Windows.
http://starship.python.net/crew/robind/wxPython/tools/
···
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
Chris Mellon wrote:
> You can't subclass from either wx.Log or wx.PyLog and have them work,
> I believe because the neccesary hooks for virtual methods aren't
> present (if you assign one as a log hander it throws an assert about
> calling undefined virtual methods, and DoLog and DoLogString aren't
> listed in it's dict).The demo uses a log derived from wx.PyLog, look in Main.py.
So it does and I have no idea what I did wrong, since I did exactly
the same thing after reading your message and it worked like a charm.
Thanks!
> I'd try to fix this myself but SWIG is still a
> great dark pit of doom to me and I think it's easy when you know how?BTW, speaking of the GDPoD I am in the process of upgrading to
1.3.27, so if anybody is using the CVS version of wxPython sources and
you need to reSWIG the .i files, you'll probably want to upgrade as
well. I've added some #ifdef's to the code that so far appear to allow
either 1.3.24, 1.3.27 or the upcoming 1.3.28 version (all with some
minor patches applied) to be used with wxPython. I've put a source
tarball of my patched version of 1.3.27 on the starship that also
includes a binary for Windows.
Any hope of your patches being applied to the official SWIG tree?
···
On 1/30/06, Robin Dunn <robin@alldunn.com> wrote:
http://starship.python.net/crew/robind/wxPython/tools/
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-dev-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-dev-help@lists.wxwidgets.org
Chris Mellon wrote:
···
On 1/30/06, Robin Dunn <robin@alldunn.com> wrote:
BTW, speaking of the GDPoD I am in the process of upgrading to
1.3.27, so if anybody is using the CVS version of wxPython sources and
you need to reSWIG the .i files, you'll probably want to upgrade as
well. I've added some #ifdef's to the code that so far appear to allow
either 1.3.24, 1.3.27 or the upcoming 1.3.28 version (all with some
minor patches applied) to be used with wxPython. I've put a source
tarball of my patched version of 1.3.27 on the starship that also
includes a binary for Windows.Any hope of your patches being applied to the official SWIG tree?
Some have been, one probably won't be. The problem is that I keep coming up with new ones.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!