vtkMapper::GetInput()

[David Gobbi]

Hi Lisa,

The wrappers don't appear to have any problems with the 
change (I know the java wrappers _would_ have problems
if it GetInput() was virtual, but then again, so would
non-ANSI C++ compilers).  So I will commit the changes.

 - David

On Fri, 7 Apr 2000, Lisa Sobierajski Avila wrote:

> Hello David,
> 
> If I remember correctly I think there was some issue with having this 
> method wrapped - because it is hidden in the subclasses by creating a 
> method of the same name with a different return type. I guess if there is 
> no problem with removing the //BTX //ETX then go ahead.
> 
> Lisa
> 
> At 12:36 PM 4/7/00, David Gobbi wrote:
> >Hi Lisa,
> >
> >I would like to remove the //BTX //ETX from vtkMapper::GetInput().
> >The reason: with vtkPicker, it is possible to query the vtkDataSet
> >of the picked actor, but I need to query the data of all the
> >actors in the vtkPicker::GetActors() collection.
> >
> >Allowing people to use
> >
> >set dataset [[actor GetMapper] GetInput]
> >
> >seems like a more elegant solution than modifying vtkPicker.  I'm
> >asking you about this because, according to the CVS logs, you
> >were the one who added vtkMapper::GetInput().
> >
> >  - David
> >
> >--
> >   David Gobbi, MSc                    dgobbi at irus.rri.on.ca
> >   Advanced Imaging Research Group
> >   Robarts Research Institute, University of Western Ontario