[vtk-developers] duplicate definition in vtkTesselatorFilter

[David C Thompson]

> Internally we fixed that by simply deleting the macro definition that is
> completely redundant, since vtkSetGet.h defines the macro to be ...
> exactly what the definition is. I guess I don't understand the need
> for both.
One is marked "const" and can thus be called when you have a "const
vtkTessellatorFilter*" while the version provided by vtkGetMacro cannot.
I seem to recall needing a const version in some of my code so I've
checked in a fix that doesn't remove the method but should prevent it
from getting wrapped. Please let me know if that doesn't fix things for
you.

	David


>  But if adding BTX/ETX pairs will stop the python dir() statement
> from reporting two methods, it does the job.
> 
> Thanks for the quick reply!
> -carlos
> 
> > Thanks. Would putting the second declaration inside //BTX ... //ETX
> > fix the problem for you?
> > 
> >     David
> > 
> > -----Original Message-----
> > From: vtk-developers-bounces+dcthomp=sandia.gov at vtk.org on behalf of Carlos Scheidegger
> > Sent: Wed 8/29/2007 2:58 PM
> > To: vtk-developers at vtk.org
> > Subject: [vtk-developers] duplicate definition in vtkTesselatorFilter
> >  
> > (Passing along a bug caught by Emanuele Santos, a colleague of mine)
> > 
> > In the CVS version of VTK, vtkTesselatorFilter has a duplicate definition:
> > 
> > class VTK_GRAPHICS_EXPORT vtkTessellatorFilter : public
> > vtkUnstructuredGridAlgorithm
> > {
> > public:
> > ...
> >   vtkGetMacro(OutputDimension,int);
> >   int GetOutputDimension() const;
> > ...
> > };
> > 
> > This is harmless enough, but the python bindings get confused and report two
> > instances of that method with the exact same type, which confuses our
> > VisTrails parser. This is a pretty minor bug, but we thought we might as well
> > report it.
> > 
> > Thanks,
> > -carlos
>