long message - double support, notifications, user feedback

[Will Schroeder]

Hi John-

A thought on point #1: can't you use MakeObject() ? This method (a 
"virtual" constructor creates another object as the same type as the 
calling object, like so:

   newPts = (vtkPoints *) inPts->MakeObject();
   newPts->SetNumberOfPoints(outSize);

(this is taken from vtkExtractGrid). Then the output type will be the same 
as the input type.

Will

>My main concern is that many many filters create an output points array
>which is VTK_FLOAT and so any data I send in gets irretrievably munged.
>Really all filters which generate PointSet or derived classes should use the
>same resolution for their outputs as for their inputs - unless there's a
>good reason!. (ignoring multiple input filters for now!).
>
>I'd like to add a function along the lines of
>CreatePointsArray()
>in vtkPolyDataSource (pointSetSource?)
>which will examine the inputs and create a points array with the correct
>type ready for the output.