Qui, 2005-04-14 às 08:53 +0200, amaury.forgeotdarc@ubitrade.com
escreveu:
> Hello,
>
> This error comes because your SWIG module doesn't share its
> types list with wxPython.
>
> When compiling the .cpp, be sure to define the symbol:
>
> SWIG_TYPE_TABLE=_wxPython_table
>
Thanks.
That was the problem.
But instead _wxPython_table, I'm using wxPython_type_table and works.
Ricardo
I'm surprised:
This value changed between 2.5.3.3 and 2.5.4.0:
"wxPython_type_table" was used for 2.5.3.3.
"_wxPython_table" is used since 2.5.4.0.
And your traceback shows a "wx-2.5.5-gtk2-unicode".
did you tweak your wx installation?
Qui, 2005-04-14 às 13:11 +0200, amaury.forgeotdarc@ubitrade.com
escreveu:
> Qui, 2005-04-14 às 08:53 +0200, amaury.forgeotdarc@ubitrade.com
> escreveu:
> > Hello,
> >
> > This error comes because your SWIG module doesn't share its
> > types list with wxPython.
> >
> > When compiling the .cpp, be sure to define the symbol:
> >
> > SWIG_TYPE_TABLE=_wxPython_table
> >
>
> Thanks.
>
> That was the problem.
>
>
> But instead _wxPython_table, I'm using wxPython_type_table and works.
>
> Ricardo
I'm surprised:
This value changed between 2.5.3.3 and 2.5.4.0:
"wxPython_type_table" was used for 2.5.3.3.
"_wxPython_table" is used since 2.5.4.0.
And your traceback shows a "wx-2.5.5-gtk2-unicode".
did you tweak your wx installation?
Readind the config.py _wxPython_table is used for MSWindows and
wxPython_type_table is used for a OS posix compliant.
Oops! They should be the same! I'll fix that. I'll make a separate variable to hold the name and then use it in both places. That way the table name will be avialable separately if anybody needs it.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!