Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 3 additions & 23 deletions development/core-concepts/nodes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,6 @@ As ComfyUI evolves, we may expand to more data types to meet the needs of more s
We provide various style settings for you to customize the appearance of nodes:
- Modify styles
- Double-click the node title to modify the node name
- Switch node inputs between input sockets and widgets through the context menu
- Resize the node by dragging any corner

<video
Expand Down Expand Up @@ -115,7 +114,6 @@ In the node's right-click context menu, you can:
In this menu, besides appearance-related settings, the following menu operations are important:

- **Mode**: Set the node's mode: Always, Never, Bypass
- **Toggle between Widget and Input mode for node inputs**: Switch between widget and input mode for node inputs

#### Mode
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:
Expand All @@ -132,31 +130,13 @@ In this comparison example, you can see that both workflows apply two LoRA model
- The node set to `Never` mode causes subsequent nodes to show errors because they don't receive any input data
- 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

#### Switching Between Widget and Input Mode for Node Inputs
### Input/Output Context Menu

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.

Here's a very simple example:

![Switch Widget and Input Mode](/images/concepts/node/switch_widget.jpg)

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.
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:

![Convert Input Mode](/images/concepts/node/convert_input.jpg)

<Note>
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
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Say goodbye to annoying widget &lt;&gt; socket conversion starting from frontend version v1.16.0! Now each widget just always have an associated input socket by default <a href="https://twitter.com/hashtag/ComfyUI?src=hash&amp;ref_src=twsrc%5Etfw">#ComfyUI</a> <a href="https://t.co/sP9HHKyGYW">pic.twitter.com/sP9HHKyGYW</a></p>&mdash; Chenlei Hu (@HclHno3) <a href="https://twitter.com/HclHno3/status/1909059259536375961?ref_src=twsrc%5Etfw">April 7, 2025</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
</Note>

### Input/Output node search

This feature is related to the data type of the corresponding input/output:
This context menu is mainly related to the data type of the corresponding input/output:

![Node Input/Output Context Menu](/images/concepts/node/context_menus_2.jpg)

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.
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.
You can adjust the number of node suggestions in the settings:

![Node Suggestion Count](/images/concepts/node/node_suggestions.jpg)
Expand Down
26 changes: 3 additions & 23 deletions zh-CN/development/core-concepts/nodes.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,6 @@ ComfyUI 正在持续开发中,文档中的部分内容可能已过时。如果
我们为提供了多种样式设置,你可以根据你的需求来设置节点的外观:
- 修改样式
- 双击节点标题修改节点名称
- 通过上下文菜单将节点输入在 input 和 组件(widget)之间进行切换
- 通过拖拽节点任意角来缩放节点尺寸

<video
Expand Down Expand Up @@ -110,7 +109,6 @@ ComfyUI 正在持续开发中,文档中的部分内容可能已过时。如果
在这个菜单中,除了外观相关的设置比较重要的是下面的菜单操作

- **模式(Mode)**: 设置节点的模式,Always、Never、绕过(Bypass)
- **切换节点输入的控件(Widget)和 输入模式**: 切换节点输入的控件(Widget)和 输入模式

#### 模式(Mode)
对于模式,你可能注意到目前我们提供了:Always、Never、On Event、On Trigger 四种模式,但实际上只有 **Always** 和 **Never** 是有效的,**On Event** 和 **On Trigger** 实际上是无效的,目前我们尚未完全实现这个功能,另外你可以把 **绕过(Bypass)** 也理解为一种模式,下面是对于几种可用模式的解释
Expand All @@ -127,31 +125,13 @@ ComfyUI 正在持续开发中,文档中的部分内容可能已过时。如果
- 被设置为 `Never` 模式的节点,后续的节点由于接收不到任何的输入数据而出现了报错
- 被设置为 `Bypass` 模式的节点,后续的节点仍旧可以获取到未经这个节点处理的数据,从而加载了第一个`Load LoRA` 节点的输出数据,所以后续的工作流依旧可以正常运行

#### 切换节点输入的控件(Widget)和 输入模式
### 输入 / 输出的上下文菜单

在有些情况下,我们需要使用来自其它节点的输出结果作为输入,此时我们就可以通过切换节点输入的控件(Widget)和 输入模式来实现。

下面是一个非常简单的例子:

![切换控件和输入模式](/images/concepts/node/switch_widget.jpg)

通过将 K-Sampler 的 Seed 从输入控件(Widget)切换为输入模式,从而统一多个节点的 seed ,实现多个采样间的变量统一。
对比第一个节点和后续的两个节点,你可以看到后两个节点的 seed 是输入模式了,同样你还可以把它再转换回控件模式:

![转换控件和输入模式](/images/zh/core-concept/node/convert_input.jpg)

<Note>
前端 v1.16.0 版本后,我们改进了这一功能,现在你只需要直接将输入端的连线直接连接到对应组件,即可完成这一过程
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Say goodbye to annoying widget &lt;&gt; socket conversion starting from frontend version v1.16.0! Now each widget just always have an associated input socket by default <a href="https://twitter.com/hashtag/ComfyUI?src=hash&amp;ref_src=twsrc%5Etfw">#ComfyUI</a> <a href="https://t.co/sP9HHKyGYW">pic.twitter.com/sP9HHKyGYW</a></p>&mdash; Chenlei Hu (@HclHno3) <a href="https://twitter.com/HclHno3/status/1909059259536375961?ref_src=twsrc%5Etfw">April 7, 2025</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
</Note>

### 输入 / 输出节点搜索

此功能与对应输入输出的数据类型相关
这里上下文菜单主要和对应输入输出的数据类型相关

![节点输入输出上下文菜单](/images/concepts/node/context_menus_2.jpg)

在拖动节点的输入 / 输出连线时,如果在画布上释放鼠标而未连接到其它节点,此时会弹出标准的节点搜索框。初始搜索结果会自动筛选显示具有兼容输入/输出类型的节点,方便你快速添加相关类型的节点
在拖动节点的输入 / 输出的时候,当有连线出现,但你未连接到其它节点的输入或输出的时候,此时释放鼠标则会弹出针对输入 / 输出的上下文菜单,用于快速添加相关类型的节点
你可以在设置中调整对应的节点建议的数量

![节点建议数量](/images/zh/core-concept/node/node_suggestions.jpg)
Expand Down