already in beta it was quite nice when creating complex nodes that you could create in- and output pins via code.
I have a exemplary usecase:
you made a patch that loads a file
the file can either contain "a string" and/or 0.1234f
you have some logic in that patch that figures out if the content represents a string or a float
the patch creates an outputpin called string and/or and outputpin called float depending on what the logic found out
those outputpins are typed as string/float accordingly
the same applies for inputpins of course, which i'd say are simpler to solve as outputpins.
i've choosen this example, because it adds extra complexity regarding generic/typed.
related:
there's already ISolution.ModifyPinGroup(NodeID, PinGroup, IsInput) and PinGroupBuilderwhich goes into that direction
I Like Dynamic Pins.
already in beta it was quite nice when creating complex nodes that you could create in- and output pins via code.
I have a exemplary usecase:
"a string"
and/or0.1234f
the same applies for inputpins of course, which i'd say are simpler to solve as outputpins. i've choosen this example, because it adds extra complexity regarding generic/typed.
related: there's already
ISolution.ModifyPinGroup(NodeID, PinGroup, IsInput)
andPinGroupBuilder
which goes into that direction