Why does the node OperatorEqual not accept the output value „ObjectSwitcher“ of the node Output2Switcher as input value?
Gruß Felix
Allplan 2024-0-1
Basically, I would say that's not your fault. I assume, everyone expects that VS should be able to convert some of the data types automatically. The ValueTypes such as RadioButtonGroup, CheckBox and different ComboBox sound weird, because they are actually used by PythonPart script to show the correct controller in Allplan Palette. That's also the reason why Boolean is currently called CheckBox in VS Editor...
VS nodes inherit that, as VS nodes and PythonPart script share the same framework. But the problem is, that VS Editor currently also uses them to detect valid connection. Therefore, you perhaps already noticed that, VS Editor sometimes won't allow some connections, even though it feels like, they should work.
However, We do plan to improve that in future.
Product Owner API, Allplan GmbH
Very simple: Because the Node OperatorEqual does not accept data of type RadioButtonGroup!
What kind of data type should that be?
Also the "accepted" so called data types of the Node OperatorEqual are a bit strange:
What should StringComboBox be for a datatype ? list of string ?
And what else should a DynamicStringComboBox be? A dynamic string ?
And this one:
PitcureResourceButtonList
PictureButtonList
PitcureResourceComboBox
PictureButtonComboBox
What is this?
And Geometric datatypes are missing entirely: Point3D, Vector3D, ...
For this you would need a threshold value (epsilon) for coordinate values.
The solution could be: Take Node RadioButtonGroup and place in front of Output2Switcher.RadioButtonGroup has an output with datatype Integer. This one you can connect to OperatorEqual.
And why the warning is occured, that an (switched) input is empty?
The warning should only occur, if the input is not connected!
What data type should that be?
My fault. I thougt that VS is smart enougt to convert data types on its own in a logical way.
For example: OperatorEqual takes the RadioButtonGroup as integer.
I was blinded by the values that show up in the picture below.
Gruß Felix
Allplan 2024-0-1
Basically, I would say that's not your fault. I assume, everyone expects that VS should be able to convert some of the data types automatically. The ValueTypes such as RadioButtonGroup, CheckBox and different ComboBox sound weird, because they are actually used by PythonPart script to show the correct controller in Allplan Palette. That's also the reason why Boolean is currently called CheckBox in VS Editor...
VS nodes inherit that, as VS nodes and PythonPart script share the same framework. But the problem is, that VS Editor currently also uses them to detect valid connection. Therefore, you perhaps already noticed that, VS Editor sometimes won't allow some connections, even though it feels like, they should work.
However, We do plan to improve that in future.
Product Owner API, Allplan GmbH
