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
Copy file name to clipboardExpand all lines: development/core-concepts/nodes.mdx
+3-23Lines changed: 3 additions & 23 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,7 +72,6 @@ As ComfyUI evolves, we may expand to more data types to meet the needs of more s
72
72
We provide various style settings for you to customize the appearance of nodes:
73
73
- Modify styles
74
74
- Double-click the node title to modify the node name
75
-
- Switch node inputs between input sockets and widgets through the context menu
76
75
- Resize the node by dragging any corner
77
76
78
77
<video
@@ -115,7 +114,6 @@ In the node's right-click context menu, you can:
115
114
In this menu, besides appearance-related settings, the following menu operations are important:
116
115
117
116
-**Mode**: Set the node's mode: Always, Never, Bypass
118
-
-**Toggle between Widget and Input mode for node inputs**: Switch between widget and input mode for node inputs
119
117
120
118
#### Mode
121
119
For modes, you may notice that we currently provide: Always, Never, On Event, On Trigger - four modes, but actually only **Always** and **Never** are effective. **On Event** and **On Trigger** are currently ineffective as we haven't fully implemented this feature. Additionally, you can understand **Bypass** as a mode. Below is an explanation of the available modes:
@@ -132,31 +130,13 @@ In this comparison example, you can see that both workflows apply two LoRA model
132
130
- The node set to `Never` mode causes subsequent nodes to show errors because they don't receive any input data
133
131
- The node set to `Bypass` mode still allows subsequent nodes to receive unprocessed data, so they load the output data from the first `Load LoRA` node, allowing the subsequent workflow to continue running normally
134
132
135
-
#### Switching Between Widget and Input Mode for Node Inputs
133
+
###Input/Output Context Menu
136
134
137
-
In some cases, we need to use output results from other nodes as input. In this case, we can switch between widget and input mode for node inputs.
138
-
139
-
Here's a very simple example:
140
-
141
-

142
-
143
-
By switching the K-Sampler's Seed from widget to input mode, multiple nodes can share the same seed, achieving variable uniformity across multiple samplers.
144
-
Comparing the first node with the subsequent two nodes, you can see that the seed in the latter two nodes is in input mode. You can also convert it back to widget mode:
After frontend version v1.16.0, we improved this feature. Now you only need to directly connect the input line to the corresponding widget to complete this process
150
-
<blockquoteclass="twitter-tweet"><plang="en"dir="ltr">Say goodbye to annoying widget <> socket conversion starting from frontend version v1.16.0! Now each widget just always have an associated input socket by default <ahref="https://twitter.com/hashtag/ComfyUI?src=hash&ref_src=twsrc%5Etfw">#ComfyUI</a> <ahref="https://t.co/sP9HHKyGYW">pic.twitter.com/sP9HHKyGYW</a></p>— Chenlei Hu (@HclHno3) <ahref="https://twitter.com/HclHno3/status/1909059259536375961?ref_src=twsrc%5Etfw">April 7, 2025</a></blockquote> <scriptasyncsrc="https://platform.twitter.com/widgets.js"charset="utf-8"></script>
151
-
</Note>
152
-
153
-
### Input/Output node search
154
-
155
-
This feature is related to the data type of the corresponding input/output:
135
+
This context menu is mainly related to the data type of the corresponding input/output:
When dragging a connection from a node's input or output and releasing it on the graph without connecting to another node, the standard node search box appears. The initial search results are filtered to show only nodes with compatible input/output types, allowing you to quickly add related nodes.
139
+
When dragging the input/output of a node, if a connection appears but you haven't connected to another node's input or output, releasing the mouse will pop up a context menu for the input/output, used to quickly add related types of nodes.
160
140
You can adjust the number of node suggestions in the settings:
<blockquoteclass="twitter-tweet"><plang="en"dir="ltr">Say goodbye to annoying widget <> socket conversion starting from frontend version v1.16.0! Now each widget just always have an associated input socket by default <ahref="https://twitter.com/hashtag/ComfyUI?src=hash&ref_src=twsrc%5Etfw">#ComfyUI</a> <ahref="https://t.co/sP9HHKyGYW">pic.twitter.com/sP9HHKyGYW</a></p>— Chenlei Hu (@HclHno3) <ahref="https://twitter.com/HclHno3/status/1909059259536375961?ref_src=twsrc%5Etfw">April 7, 2025</a></blockquote> <scriptasyncsrc="https://platform.twitter.com/widgets.js"charset="utf-8"></script>
0 commit comments