GU Text Edit:
G_TextEdit lets you work with incoming text through an editable node interface and pass the resulting text to the next part of your workflow. It is intended for situations where you want to revise text without changing its upstream source. The node description also identifies protecting edited text from being refreshed on the next queue run as a goal; the supplied Python code does not show how that protection is implemented, so the exact behavior may depend on the accompanying editor interface.
GU Text Edit Input Parameters:
only
A STRING field displayed as a single-line widget, with the default value dynamic text edit !. The supplied execution code receives this value but does not read it when choosing the outgoing text, so changing it alone has no demonstrated effect on the result. No minimum or maximum length is specified.
text
The required incoming STRING, configured as a multiline input connection rather than a freely editable widget. The node uses its first received text value as the initial outgoing value. If edited content is available from the node’s editor interface, that content replaces the initial value. Connect the text you want to review or edit here. No default, minimum length, or maximum length is specified.
protect
A BOOLEAN widget with the options True and False; its default is False. The node’s description associates protection with keeping edited text from refreshing on the next queue run. However, the supplied execution code does not read this setting, so its effect cannot be confirmed from this source alone. There are no numeric minimum or maximum values.
GU Text Edit Output Parameters:
text_out
A STRING containing the text selected by the node. Normally, it starts as the first value received through text; when the node can retrieve edited content from its editor interface, that edited content takes precedence. Connect text_out to a downstream text or prompt input to use the resulting wording. Although the node accepts list-form inputs internally, this output is declared as a single value, not a list of separate text outputs.
GU Text Edit Usage Tips:
- Connect a text-producing node to
text, then connecttext_outto the prompt or other text-consuming node where you want the revised wording to be used. - If you edit text in the node’s interface, run the workflow and check the downstream result: the supplied code uses retrieved editor content when available, otherwise it passes through the first incoming text value.
- Treat
protectas an interface setting whose effect should be verified in your installed version. Test it by editing the text, queuing the workflow again, and checking whether your edit remains. - Do not rely on changing
onlyto altertext_out; the supplied execution code does not use that field to select the output.
GU Text Edit Common Errors and Solutions:
Required input is missing: text
- Explanation:
textis a required connection, so the workflow may fail validation or be unable to run if nothing supplies it. - Solution: Connect a node that produces a STRING to
text, then queue the workflow again.
TypeError: 'NoneType' object is not subscriptable
- Explanation: The code reads the first item of
textand the hidden workflow data. If any of those expected values is missing, indexing it can raise this error. The exact cause depends on which value was absent. - Solution: Check that
textis connected, then rerun the workflow. If the error persists, reload the workflow and verify that the node is running in a compatible ComfyUI environment with its required node-pack files available.
IndexError: list index out of range
- Explanation: The node takes the first item from
textand from hidden workflow data. An empty list in one of those positions can cause this error. - Solution: Ensure the upstream text connection supplies a value. If it does, reload or recreate the node and try again.
Edited text is not reflected in text_out
- Explanation: The node passes through the first incoming text value unless it can retrieve edited content from its editor interface. The supplied source does not establish why an edit might be unavailable.
- Solution: Confirm that the edit appears in the node interface, queue the workflow again, and inspect the connected downstream text. If it still passes through the original text, check that the node pack’s interface components are installed and loaded.
Changing only or protect does not change the output
- Explanation: Neither field is read by the supplied Python execution code when it chooses
text_out. Any behavior provided by the editor interface is not established by this source. - Solution: Supply the wording through
textor the node’s editor interface, and verify protection behavior with a queue-run test rather than assuming the setting changes the outgoing text.
