- Dec 05, 2024
-
-
Jean Fechter authored
-
- Dec 02, 2024
-
-
Jean Fechter authored
-
- Nov 29, 2024
-
-
(cherry picked from commit 8ec1d44d)
-
Fix a bug where the cut plane wasn't considered as intersecting HTG cells due to precision loss during floating point comparison. (cherry picked from commit 08a5f4aa)
-
(cherry picked from commit e6f61ea5)
-
(cherry picked from commit facca32c)
-
(cherry picked from commit 0692322c)
-
Jean Fechter authored
-
- Nov 27, 2024
-
-
Jean Fechter authored
-
Jean Fechter authored
-
- Nov 26, 2024
-
-
Spiros Tsalikis authored
-
Spiros Tsalikis authored
-
- Nov 22, 2024
-
-
Jean Fechter authored
-
Jean Fechter authored
-
Mohamed Mssaouri authored
-
- Nov 18, 2024
-
-
Thomas Galland authored
-
Thomas Galland authored
Fix a bug where the cut plane wasn't considered as intersecting HTG cells due to precision loss during floating point comparison.
-
Jean Fechter authored
-
Jean Fechter authored
-
- Nov 15, 2024
-
-
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
-
Andras Lasso authored
VTK users may not be aware that the contour tringulator is often a superior replacement for 2D Delaunay. See https://discourse.vtk.org/t/constrained-vtkdelaunay2d-failure-with-3-holes-bug-use-vtkcontourtriangulator-instead/14834/5
-
Jean Fechter authored
-
Jean Fechter authored
-
- Nov 14, 2024
-
-
Mathieu Westphal (Kitware) authored
Add a LPT::ForcePManualShift option and add tests for it
-
- Nov 13, 2024
-
-
Mathieu Westphal (Kitware) authored
-
- Nov 08, 2024
-
-
(cherry picked from commit 53da5dfd)
-
An INFO message is always printed with default log verbosity. This INFO message was in a function that checks a capability, so could be logged during the course of an entirely normal operation. This changes it to TRACE to quiet it but still make it available at higher verbosity levels. (cherry picked from commit 894fa2de)
-
Specially for Composite sublcasses: if class change, but not the content (same leaves etc), cache status reflect that and be disabled (cherry picked from commit 06ee0008)
-
The previous GetCellAtId() calls were not thread safe unless the cell array type matched vtkIdType. To work around this, the caller must supply storage for the cell Ids. (cherry picked from commit 605de6e4)
-
(cherry picked from commit a5e4bce9)
-
(cherry picked from commit 7e41d629)
-
(cherry picked from commit 35c93c98)
-
(cherry picked from commit 45bb0d8f)
-
This allows `grep` to find what needs updated when removing deprecated-in-9.4 APIs. (cherry picked from commit c1b188fb)
-
(cherry picked from commit a3836e3b)
-
(cherry picked from commit 6fea24e9)
-
(cherry picked from commit 55877f23)
-
- Nov 07, 2024
-
-
Nicolas Vuaille authored
It is used for performance. So debugging often occurs while using Release build and not Debug. Using classical Log macro instead of the vtkDebugMacro allows to get log even in Release build Relying on this->Debug allows to filter in only relevant instances
-
Nicolas Vuaille authored
One cannot compare Cache and Original data type: the consumer can change it! E.g. ExtractSurface can have an UG as Original data but has a PolyData as Cache. What we want to check here is only input type across different executions. So put the check in SetOriginalData instead and invalidate the Cache as needed
-
- Nov 04, 2024
-
-
Jean Fechter authored
-