[Feature Request]: Allow widget values to be forwarded to other nodes

[iamrohitanshu]

Is there an existing issue for this?

• [x] I have searched the existing issues and checked the recent builds/commits

What would your feature do ?

This feature will allow the user to take the value of a manually input widget (of a node), and forward it to other nodes. Thus, no useful information is lost on a node, and can be forwarded if needed.

Proposed workflow

See the concept image below, in which the value of the 'width' widget of the 'Empty Latent Image' node is being forwarded to the 'a' input of the 'Math Expression' node.

I don't know all the output types, but even if they are capped to only the basic types, i.e. INT, FLOAT and STRING, it would still be a great.

Additional information

This feature will not only help in decreasing nodes, and saving metadata info, but it will also minimize the vertical length of nodes where output values are already put in widgets, like 'Get Image Size' and 'Rescale/Resize Image' type nodes.

┆Issue is synchronized with this Notion page by Unito

[tajino]

Having this would be very useful, not just forwarded to other nodes, the implementation should also allow using one output into another input of the same node.

For example :

In the Empty latent image, one could use the output of Height and connect it to input of Width, to sync up both width and height, by just changing the height value, the weight will follow, or do some simple math in between to add some value to the Height output before inputting to the Width input of the same node. A process that currently takes 3 nodes to accomplish, can be reduced to 2.

I would rather see this implemented sooner, than having selection toolbox, tooltips, templates, first time user landing page, etc.

[Tekaiguy]

I'm sorry but this is brilliant. It consolidates the same functionality of nodes and expands to make them even more flexible all while remaining as intuitive as ever. In my heart, I wanted this to be the case all along, but I just figured: "If it was possible, surely they would have included it by now". Seeing this request has re-ignited that vision. Also, decreasing the vertical length of nodes would be HUGE for UI Andy's.

[without-ordinary]

+1 for something like this.

Saves having to either find/create a custom node that has them as normal outputs, or adding a layer of primitives/value literals ahead of the node, or having to find/create a node which can get the values from the normal output (like a node which returns the latent resolution)