Ability to detach constant value flags and connect them to multiple nodes

[root (Team Vuo)]

.

[jersmi]

How is this different from Share Value?

[jstrecker (Jaymie)]

A couple ways — Share Value requires an event to make the data go out the output cable, detached constant value flags would not. Share Value requires creating and connecting that node (at a minimum, right-clicking on canvas, selecting the menu option, and connecting to an input port), whereas detaching a constant flag would just require dragging it off of the input port.

[Bodysoulspirit]

Had been wondering too …

Whereas detaching a constant flag would just require dragging it off of the input port.

Equivalent to QC Input Splitter then ? Perhaps add something like that in the title for all the QC users to know of. Smtg like.

“Input / Output Ports Splitter - Detach constant values to connect to multiple nodes”

[Bodysoulspirit]

A couple ways — Share Value requires an event to make the data go out the output cable, detached constant value flags would not.

Why would it not ? What would be the benefit of not ? Just asking.
You mean won’t need an event when editing a composition ? or also as exported ?

[jstrecker (Jaymie)]

Equivalent to QC Input Splitter then ? Perhaps add something like that in the title for all the QC users to know of.

@Bodysoulspirit, I added it to the “equivalents” section so now it shows up near the top of this page. Hope that’s OK.

Share Value requires an event to make the data go out the output cable, detached constant value flags would not.

Why would it not ? What would be the benefit of not ?

The benefit is not having to connect as many cables. Here’s an example showing how Share Value needs a cable with an incoming event to work…

… whereas a detached constant flag would not…

[useful_design (Alastair)]

@jstrecker “Share Value requires an event to make the data go out the output cable, detached constant value flags would not.”

Does that mean that flags would ‘fire’ data+event every time the window they are (ultimately) connected to generates a new ‘frame’? This gets back to that whole big discussion about updating node input port values and needing an event for the scene to re-evaluate to take account of the the node input value(s). And could a node (hypothetically) determine which Window it’s connected to at the end of the event chain and therefore assume the same fire rate for its evaluation auto-trigger?

I’m not sure I understand how shared values and constant value flags would differ in terms of adjusting a value and having nodes re-evaluate. Also would constant value flags themselves be able to take a wire at an input or would they always be manual entry in the graph editor only?  

[jstrecker (Jaymie)]

@useful_design, detached constant flags would behave the same as regular constant flags do now. If you edit one while the composition is running, the node immediately starts using the new value. (Fire an event from Node when an input value is changed in the Editor will have been implemented by the time we add detached constant flags.)

Constant flags wouldn’t be able to take a cable. You’d still use Share Value for that. (I anticipate needing some way to easily switch between the two…)

[useful_design (Alastair)]

Might like to consider my FR for detachable Drawers as nodes in conjunction with this FR. Very similar concept, had forgotten this one when I got around to logging FR for detached Drawers.