[vtkusers] VTK 5.4.2

Zack Galbreath zack.galbreath at kitware.com
Thu Jun 4 14:30:17 EDT 2009

Dear VTK users and developers,

The VTK 5.4.2 patch release is now available for download from the VTK 
web site: http://vtk.org/VTK/resources/software.html .  A full list of 
changes are included at the end of this message.

We hope you enjoy this new release of VTK.


Instead of deleting timers immediately, mark them for deletion next time 
the event loop is entered.

When a user transform is applied to vtkAxesActor, make sure the axis 
labels are translated with the axes

Fix a memory leak

Bug fixes courtesy of Terry Jordan.

The first set of changes is necessary because for some reason this 
reader never supplied ParaView with its number of cells.

The second set of changes is necessary because it seems now that we have 
either encounter errant fluent files or an error in their writer or 
possibly some change to there file formatting that no longer supplies 
the index within the end of binary section entry.  This patch is 
backwards compatible and has worked on all data sets tested.

Also fix uninitialized this->NumberOfCells. As this is used in 
PrintSelf. Detected by valgrind on otherPrint.

*Rendering/vtkCameraActor.cxx & Rendering/vtkLightActor.cxx*
Changed vtkErrorMacro into vtkDebugMacro to avoid printing error in the 
context of just creation an object followed by Print(). It happened 
because PrintSelf on the actor calls PrintSelf on superclass, which call 
GetBounds, which call UpdateViewProps() on the concrete classes 
vtkLightActor and vtkCameraActor.

Fix location for mouse events, bug #8261.

library VERSION and SOVERSION consistent with other vtk utility 
libraries on Linux builds.

Check for a null pointer

*Widgets/vtkLineRepresentation.h & Widgets/vtkLineRepresentation.cxx*
Computation of parameteric coordinate: t and the closest_point was done 
in display coordinates. The value t cannot directly be mapped to word 
coordinates, since it needs to be scaled according to the projection 
matrix. (The farther you go from the camera position, the larger the 
increments in t). To avoid this, keep everything in word coordinates by 
using a picker.

More information about the vtkusers mailing list