Skip to content

Conversation

@DN2048
Copy link

@DN2048 DN2048 commented May 2, 2024

Hello! I added a seed history to the Seed widget because it’s a feature that I find useful. Here’s my situation: I generate an image and it looks very nice but what if the next seed generates something better? So I generate a new one, do some tweaking to the workflow, generate again, more tweaking and nah; that first seed was the best. I want to go back to it but what was that seed? I could use the workflow history or some custom node that keeps a log/gallery of what I did but I don’t want to lose all the small tweaks I did after that because all of these solutions will also restore the workflow. I didn’t find a node that would restore just the seed. I could load the image somewhere else to get just the seed but that’s too many steps. Why not just have a simple, easy to use, seed history? And this feature is just that.

As it is right now, I replaced that textbox with the last seed with a combobox where you have all the last 50 seeds (can be changed in code). When you select a seed it will replace the current seed like if you pressed the “use last queued seed” button. When the number of seeds goes over 50, the last one is removed from the list.
If the new seed used is the same as the last one, it won’t be added to the list.
The history only works if the option is active.
no_history
history
history_combo
history_bigger_combo

I would like to know your thoughts. Do you want to add this feature? Maybe change the way it’s implemented?
I haven’t implemented this in Python and TypeScript because I first wanted your opinions. If you guys give it a go I’ll also update for those two (even though I don’t know where/how to test them, I only use the web-ui).
Also, I’m not a JavaScript developer so if there are “better ways” to do something that I implemented I’m open to suggestions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant