Glad to see you're getting to the bottom of this. I
imagine this won't
be the last time different hierarchies will bite us in the
butt. I'm
taking a bit of time to get more familiar with Swig so that
I won't feel
so lost when we get into the object tracking portion.
Kevin Smith wrote:
> On Sun, 2006-04-09 at 22:33 -0400, Kevin Smith wrote:
>
>> This one is driving me INSANE. When I made this
same change, my compiler
>> (gcc 4.0.2 I believe) complains that wxControl is
not a base class of
>> wxTreeCtrl. But *it is*. I have a couple things
left to try, but at this
>> point I am completely confused. It knows that
wxWindow is an ancestor,
>> but not wxControlBase or wxControl. ARGH!
>>
>
> Quick update: I haven't solved it, but at least I know
mostly what is
> going on. With my wx installation, for whatever reason,
wxTreeCtrl
> inherits from wxGenericTreeCtrl, which inherits from
wxScrolledWindow.
> So it bypasses wxControl, which means our
classes/include/wxTreeCtrl.h
> is incorrect.
>
> Hopefully later this week I'll be able to go back and
fix this, somehow.
> Hopefully in a way that will work on all platforms.
>
> By the way, the tool I used to figure this out was to
add -E to the
> compiler flags. That sends the preprocessor results to
the .o file
> instead of actual object code. With that, I was able to
see the actual
> class hierarchy, rather than the one that I thought I
was seeing when I
> looked at the wx header files.
>
> Kevin
>
>
> _______________________________________________
> wxruby-users mailing list
> wxruby-users rubyforge.org
> ht
tp://rubyforge.org/mailman/listinfo/wxruby-users
>
>
>
>
_______________________________________________
wxruby-users mailing list
wxruby-users rubyforge.org
ht
tp://rubyforge.org/mailman/listinfo/wxruby-users
|