[vtk-developers] vtkCleanPolyData

Bill Lorensen bill.lorensen at gmail.com
Thu Apr 23 17:11:03 EDT 2009


This definitely looks like a bug. I think in ITK we would also fix this one.

Bill

On Thu, Apr 23, 2009 at 5:05 PM, Berk Geveci <berk.geveci at kitware.com> wrote:
>> I am more familiar with ITK where the approach to
>> backwards-compatibility is that it should always be maintained.
>> Changing the type of data returned from a filter is a pretty drastic
>> move, even if -- in most cases -- it doesnt break anything obvious.
>
> VTK approach is different. We break backwards compatibility to fix
> behavior we believe is wrong. VTK used to assume that all point
> coordinates were single precision. To overcome precision issues, many
> of the new readers can now provide double precision floats. The right
> behavior for a filter is to preserve the precision of its input. This should
> have been done for all filters long time ago but we have limited resources.
>  Adding a switch to a filter is an ugly, duct-tape solution that will
> burden all current and future users. Keep in mind that this will have a
> very minor impact on compatibility as most "legacy" codes that use VTK
> will produce single precision points.
>
> -berk
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtk-developers
>
>



More information about the vtk-developers mailing list