From d5b388a61e93abb59c9da2f16b73802fb1c3c028 Mon Sep 17 00:00:00 2001 From: Kenneth Moreland Date: Tue, 8 Feb 2022 13:43:33 -0700 Subject: [PATCH] Support backward compatibility with PointElevation filter The interface for `PointElevation` changed the `SetLowPoint` and `SetHighPoint` methods to accept a `vtkm::Vec3f_64` instead of 3 `vtkm::Float64`. This means all code using `PointElevation` wrong. Why not have both? --- vtkm/filter/field_transform/PointElevation.h | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/vtkm/filter/field_transform/PointElevation.h b/vtkm/filter/field_transform/PointElevation.h index 587b76e25..ab65af573 100644 --- a/vtkm/filter/field_transform/PointElevation.h +++ b/vtkm/filter/field_transform/PointElevation.h @@ -33,11 +33,17 @@ public: VTKM_CONT PointElevation(); - VTKM_CONT - void SetLowPoint(const vtkm::Vec3f_64& point) { this->LowPoint = point; } + VTKM_CONT void SetLowPoint(const vtkm::Vec3f_64& point) { this->LowPoint = point; } + VTKM_CONT void SetLowPoint(vtkm::Float64 x, vtkm::Float64 y, vtkm::Float64 z) + { + this->SetLowPoint({ x, y, z }); + } - VTKM_CONT - void SetHighPoint(const vtkm::Vec3f_64& point) { this->HighPoint = point; } + VTKM_CONT void SetHighPoint(const vtkm::Vec3f_64& point) { this->HighPoint = point; } + VTKM_CONT void SetHighPoint(vtkm::Float64 x, vtkm::Float64 y, vtkm::Float64 z) + { + this->SetHighPoint({ x, y, z }); + } VTKM_CONT void SetRange(vtkm::Float64 low, vtkm::Float64 high)