This script will do an in-place replacement of "import vtk" with
statements like "from vtkmodules.vtkCommonCore import vtkObject",
along with replacement of usages like "vtk.vtkObject" throughout
the code with "vtkObject".
254f47d792 vtkContour3DLinearGrid: Interpolate Cell Data
9baa5c5e80 vtkContour3DLinearGrid: Use active scalars if array has no name
63adce266d vtkFlyingEdges3D: Interpolate also CellData
04311d6d67 Add changelog
5008ea905f vtkContourFilter: Delegate to vtkFlyingEdges2D/3D and vtkContour3DLinearGrid
143aaa891b vtkContour3DLinearGrid: Use ArrayDispatch
94b15ea437 vtkContour3DLinearGrid: Remove duplicate code present in ProcessPiece
f6aa9015aa vtkContour3DLinearGrid: Use vtkSet/GetMacro for OutputPointsPrecision
...
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Reviewed-by: Cory Quammen <cory.quammen@kitware.com>
Merge-request: !9687
- Enable OpenXR in fedora standard CI
- Introduce new OpenXR/OpenVR tests and CMake options to control which test to run
- Only instanciation tests are run in CI for now, rendering tests are not run in CI yet.
- Rendering test do not require to set HMD position as they render a sphere which looks the same from wherever
- Fix action .json files location in build and install so it can be used in tests
- Fix multiples issues with Initialize/Finalize code
- Fix issues with Render method virtual logic
- Add baselines for index, mixed reality and monado (openxr only)
- Tested with ParaView XRInterface plugin manually
Previously, there was no progress updates when the input was an
unstructured grid. This commit fixes the issue by forwarding the progress
updates of the internal filter to vtkContourFilter.
The OBJ in issue #18762 has no vertex normals, yet its faces contain
invalid reference numbers to them. This leads to a non-zero n_normal_pts
and a null normals buffer in vtkOBJReader.
Fix the "Grounded" movement bug, that was not working with OpenXR selected as backend.
The reason was the HeadSetDir variable, that is needed for movement computations,
was never set in the vtkVRInteractorStyle with OpenXR.
This simply get the HMD pose (for now left eye) from the runtime and
emits a new event in vtkOpenXRRenderWindowInteractor::PollXrActions.
cc1dc63a6d Use 'override' for Python test interactor
ed84c0269d Fix Python overrides that use existing name
Acked-by: Kitware Robot <kwrobot@kitware.com>
Acked-by: buildbot <buildbot@kitware.com>
Reviewed-by: Bane Sullivan <bane.sullivan@kitware.com>
Reviewed-by: Berk Geveci <berk.geveci@kitware.com>
Merge-request: !9838
In rtImageTest.py, vtk.vtkRenderWindowInteractor was being replaced
with a vtkTestingInteractor class by simply inserting the latter
into the 'vtk' module. This is unsuitable for modern tests, which
don't use the 'vtk' module. Instead, the 'override' function must
be used to robustly override the interactor.
The 'override' function in the wrappers has a check to ensure that
users don't override one wrapped C++ class with another wrapped
C++ class (see a4b954b8). The overriding class must be a Python
class that is a subclass of the overridden C++ class.
However, rtImageTest.py defined a class called vtkTestingInteractor
and an override with this class failed because within VTK there is
a class called vtkmodules.vtkTestingRendering.vtkTestingInteractor.
The check has to consider not only the name, but also the type, or
else it will get false positives.
Cells are created with points of double type. EvaluateLocation/Position
functions assume that the points are of double type to avoid copying
and using virtual functions
Spiros Tsalikis
Thomas Galland
Kitware Robot
Sean McBride
David Gobbi
Will Schroeder
Yohann Bearzi
Caitlin Ross
Ryan Krattiger
Mathieu Westphal
Christos Tsolakis
Qiao Tan
Timothee Chabat
Ben Boeckel