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: more_math/ImageMathNode.py
+2-6Lines changed: 2 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -19,11 +19,7 @@ class ImageMathNode(io.ComfyNode):
19
19
@classmethod
20
20
defdefine_schema(cls) ->io.Schema:
21
21
returnio.Schema(
22
-
node_id="mrmth_ag_ImageMathNode", # New ID to avoid collision if necessary, or keep standard and user migrates? User asked to "switch", likely implies replacing functionality but maybe keeping ID? Usually replacing ID breaks workflows.
23
-
# Strategy: Use a NEW ID for the autogrow version if we want to allow side-by-side, but typically "Autogrow switch" implies replacing the main node.
24
-
# However, standard ComfyUI practice for breaking changes is often a new node or careful migration.
25
-
# Looking at AudioMathNode in step 6, it used "mrmth_ag_AudioMathNode".
26
-
# I will follow that pattern: mrmth_ag_ImageMathNode.
0 commit comments