-
Notifications
You must be signed in to change notification settings - Fork 185
Why are the operator properties static? Can't we use a state to set them up dynamically at runtime before launching the region? So every operator always has an input port/output port for this purpose and all operators are the same
All reactions
Replies: 2 comments 14 replies
Please use an example operator and a screenshot to explain the question.
All reactions
Can you put file scan and file scan with input operators side by side and take a screenshot?
All reactions
Reason?
All reactions
All reactions
If we make the filename input as optional, is that what you want? From my understanding, you want to have a source operator with input port.
All reactions
No, that is not what I mean.
I want to setup any operator dynamically, regardless of input ports.
All reactions
It's actually on our road map. For example, we want to allow user to type variable "i" in the property panel of any operator inside a for loop.
All reactions
variable "i" or state "i"?
All reactions
Only inside loop?
All reactions
variable "i" or state "i" is referring to the same thing.
Loop is just one example. It should work without loop.
All reactions
What will be the specific syntax for it be? like if the property is a string, something like states["i"]?