You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
flow New input does not eject a value box meaning you cant pull a connection off of them. and must use the input or output of another node. this also has a side effect of not being able to make a "passthrough" flow there implementation details get filled out later.
The text was updated successfully, but these errors were encountered:
What you refer to as the "value box" is what I call a "pin" (or inport/outport in FBP lingo
Main inputs/outputs can be thought of floating inport/outports.
I'll start with the second issue - a valid (and relatively easy) bug. Creating passthrough nodes is a very interesting motivator for fixing that.
The first issue is more thought-provoking as it raises questions regarding the whole implementation of main inport/outports, which TBH I am not 100% happy with:
it's hard to understand
it creates issues like a conflict between the drag behavior and drag-to-connect behavior
The only alternative I can think of is a built-in node that exposes main inputs or main outputs, which I am not happy with either
flow New input does not eject a value box meaning you cant pull a connection off of them. and must use the input or output of another node. this also has a side effect of not being able to make a "passthrough" flow there implementation details get filled out later.
The text was updated successfully, but these errors were encountered: