Hi,
Looks like I may have incorrectly explained my point.
What I mean to say is that sometimes a property can be split in multiple parts, then it definitely makes sense to have multiple ways to set it. But two different, unrelated, properties should not be related API wise.
eg:
A filter has two properties, Foo and Bar.
Foo is an int[3] that can be decomposed in Foo1, Foo2 and Foo3.
Bar is only a string property.
The expected API would look like this:
SetFoo(int* foo);
SetFoo(int foo1, int foo2, int foo3);
SetFoo1(int)
SetFoo2(int)
SetFoo3(int)
SetBar(const char*)
What would be not expected would be:
SetFooAndBar(int*, const char*);
I hope we can agree on this.
If that is the case, then we can discuss about the vtkThreshold specifically and if ThresholdFunction and ThresholdValue can be considered two different properties or a single property that is can be decomposed in multiple parts.
I believe that it is indeed two properties.
@lassoan thinks that it is a single property and that it should be possible to set it together.