[vtk-developers] Proposed filter name and class hierarchy changes

[John Platt]

Hi,

Thanks for that - I only work with explicit point sets vtkPolyData &
vtkUnstructuredGrid which are special cases. An option to preserve input
type would be very useful. It would also be nice to have a "SelectAll"
which just points the output to the input. You can then leave the filter
in the pipeline with little overhead when selections are not required.

John.

-----Original Message-----
From: vtk-developers-bounces+jcplatt=dsl.pipex.com at vtk.org
[mailto:vtk-developers-bounces+jcplatt=dsl.pipex.com at vtk.org] On Behalf
Of David E DeMarle
Sent: 06 February 2007 23:00
To: vtk-developers at vtk.org
Subject: Re: [vtk-developers] Proposed filter name and class hierarchy
changes

Hello,

It is because when you take a generic subset out of a structured data
type the output geometry is not necessarily going to stay structured.
Taking just the voxels with a particular range of values out of an
image data can create a blob of voxels that does not completely cover
any cubical volume for instance. Thus the output type has to be
unstructured grid, which can represent any shape.

I am considering giving all of the new vtkExtractSelected* filters a
"PassThrough" which will preserve the input data type and just add new
attribute arrays. vtkFrustumExtractor has this now.

thanks,
Dave DeMarle
_______________________________________________
vtk-developers mailing list
vtk-developers at vtk.org
http://www.vtk.org/mailman/listinfo/vtk-developers