-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The "GlobalSeed" node doesn't work with grouped nodes #80
Comments
I'm having this problem too, but not with a grouped node. I think it's a logic error in the global seed handler. Take a look at the current version below. It iterates through all nodes and collects the values from the GlobalSeed node when it encounters it, but that means ignoring all the nodes that it passes until then because w will be undefined. Most straightforward approach is to find the values from the global seed widget first and then iterate through the nodes
|
That part is simply about reflecting the workflow update information received from the backend into the workflow. The update information includes details on how to update each widget of the nodes, so the order doesn't matter. The actual update of the seed occurs when the prompt is sent to the backend and before the prompt is executed.
|
Group nodes are dynamically generated and executed in the form of virtual nodes, which is a special structure. Currently, the functions processed right before the prompt execution (global seed, onprompt, ...) do not take group nodes into account. |
thanks @ltdrdata. I wasn't using a group node. I'll try to replicate it and see what I find |
As per the title, it has no effect on grouped nodes. Stage B in the image is a grouped node...
The text was updated successfully, but these errors were encountered: