wxruby users - Sep 2005 - The problem with %import

Here''s an example of the problem I was talking about the other day.  
Take a look at Button.i.  It imports from its entire heirarchy.  If you 
look at Button.cpp you will see that no wrappers are generated for 
anything except the button functions.

This brings up some other things that we''ll need to keep in mind:   If 
we''ve created a typemap in a .i file in classes and the .h file for
that
class is %imported elsewhere, we''d need to either redeclare the typemap
or we''ll need to place them into a file that gets %included  (e.g.:  
%include "..\Window_typemaps.i")

Roy

Roy Sutton wrote:
> This brings up some other things that we''ll need to keep in mind: 
If
> we''ve created a typemap in a .i file in classes and the .h file
for that
> class is %imported elsewhere, we''d need to either redeclare the
typemap
> or we''ll need to place them into a file that gets %included 
(e.g.:
> %include "..\Window_typemaps.i")
My inclination is to move *all* the typemaps out of the individual .i 
files and put them all in swig/typemaps.i so they are available to any 
class that needs them.

I guess the only exception would be if there were two classes that 
needed similar but incompatible typemaps, but I can''t think of any 
situation that would require that.

Unless there''s a reason to keep typemaps in individual class .i files, 
I''ll probably start rejecting any patch that adds more. And would start
moving typemaps into .i files (or hoping to get patches to do so).

Cheers,

Kevin