Skip to content
Snippets Groups Projects
  1. Nov 29, 2024
  2. Nov 28, 2024
  3. Nov 22, 2024
  4. Nov 20, 2024
  5. Nov 19, 2024
  6. Nov 18, 2024
  7. Nov 15, 2024
    • Jaswant Panchumarti (Kitware)'s avatar
      Make vtkCameraOrientationWidget robust for deserialization · 9856f6f6
      Jaswant Panchumarti (Kitware) authored
      - This commit is a first step to getting the widget to deserialize
      correctly because during deserialization a different renderer
      is assigned as the default renderer.
      - When another renderer is provided, this commit carefully removes
      the previous reorientation observer. If the widget was previously
      enabled, it replaces the older renderer in the render window with the
      new renderer. Otherwise, upon deserialization, the render window had
      an extra renderer which originated from the constructor of
      `vtkCameraOrientationWidget``.
      - Updated baseline images which used the camera orientation widget
        because the widget now resizes itself to correct proportions
      9856f6f6
  8. Nov 14, 2024
  9. Nov 08, 2024
  10. Nov 07, 2024
  11. Nov 05, 2024
  12. Oct 30, 2024
    • Jean Fechter's avatar
      446e4f51
    • Léon Victor's avatar
      Fix int overflow and perf improvements · 7632488d
      Léon Victor authored and Jean Fechter's avatar Jean Fechter committed
      The tetrahedron reading logic used a non-tetrahedron-specifc `vtkUnstructredGrid::InsertNextCell` call which performed poorly due to a large amount of time spent managing a `std::set`, and struggling with memory allocation previsions.
      
      With this change we instead handle the cell ID uniqueness ourselves and use the tetrahedron-specific API, resulting in a 2~3x speedup on a large dataset.
      
      The logic is also refactored a bit for readability
      
      Fix an int overflow that could occur when seeking a very large offset (it did happen in the geometry file)
      
      Overall performance improvements
      7632488d
  13. Oct 28, 2024
  14. Oct 27, 2024
    • Cory Quammen's avatar
      vtkLog: sweep to change INFO log messages to TRACE · 162132e1
      Cory Quammen authored
      INFO log messages will be logged by default to stdout, but this
      logging level was used in a number of places throughout VTK, leading
      to unexpected output messages. VTK should not print messages to stdout
      by default except when reporting a warning or error condition. This
      commit changes messages that do not report warnings/errors to TRACE so
      messages will be logged only when the logging level is specifically
      requested to be more verbose.
      162132e1
  15. Oct 24, 2024
Loading