[vtkusers] vtkPoints.SetPoints bug?

[David Gobbi]

Hi Eric,

It's necessary to call Modified() after calling SetPoint() in order for
ComputeBounds() to re-compute the bounds.  This is because ComputeBounds()
checks the timestamp and does nothing if the timestamp shows that the
previous bounds are still good.

As far as I understand, vtkPoints has behaved this way for many years.
Recently, however, there have been many changes to the VTK rendering
pipeline that increase the reliance on timestamps. Perhaps in VTK 8.0
something was triggering a Modified() call or was otherwise forcing a
re-computation of the bounds.

  David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://public.kitware.com/pipermail/vtkusers/attachments/20181125/0d4b1584/attachment.html>