VTK, the premiere data visualization library, has just released verion 5.4.2 with improved readers for Fluent and other changes.  Various memory leaks and UI glitches have been fixed, and the code is all online and ready for download.

You can read the complete changelog after the break.

Kitware – News.

  • *GUISupport/Qt/QVTKWidget.cxx*
    Instead of deleting timers immediately, mark them for deletion next time the event loop is entered.
  • *Hybrid/vtkAxesActor.cxx*
    When a user transform is applied to vtkAxesActor, make sure the axis labels are translated with the axes
  • *Infovis/vtkCommunity2DLayoutStrategy.cxx*
    Fix a memory leak
  • *IO/vtkFLUENTReader.cxx*
    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 inPrintSelf. 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.
  • *Rendering/vtkCarbonRenderWindowInteractor.cxx*
    Fix location for mouse events, bug #8261.
  • *Utilities/CMakeLists.txt*
    Use VTK_LIBRARY_PROPERTIES value for VERDICT_LIBRARY_PROPERTIES. Makes verdict library VERSION and SOVERSION consistent with other vtk utility libraries on Linux builds.
  • *Views/vtkGraphLayoutView.cxx*
    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.

From the VTKUsers Mailing List.

Tags