[vtkusers] vtkPoints.SetPoints bug?

[Fahlgren, Eric]

Thanks, David, that fixes it.  I’m pretty surprised at this since the code was actually written back in the 5.2 days and hasn’t been touched since…

Eric

From: David Gobbi [mailto:david.gobbi at gmail.com]
Sent: Sunday, November 25, 2018 8:25 AM
To: Fahlgren, Eric
Cc: vtkusers at public.kitware.com
Subject: Re: [vtkusers] vtkPoints.SetPoints bug?

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/9467a8ff/attachment.html>