It was just a convenience function. There was no direct triggering of any computation.
Correct I mispoke, however the problem was that with one method you control two parameters, which is definitely non-standard for a vtk filter. However in that context they could have been conserved but we made the conscious choice to remove them choosing to have a better API in the expense of changing it.
The same
ThresholdByUpper(),ThresholdByLower(),ThresholdBetween()methods are still used in vtkImageThreshold.
It should be changed too.
. According to VTK style, these methods should have been added:
SetThresholdFunctionToBetween()
SetThresholdFunctionToUpper()
SetThresholdFunctionToLower()
Definitely ! That is a needed adition to make the API better. I’d gladly review a MR adding that in.