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
Style manager #3062
Comments
It would be great if the manager had two text fields to edit / update the pos & neg prompts of a style |
Even a text box kind of ui to edit the csv is okay for me. |
Added in 20549a5 |
That style manager/editor is nice, but... it did killed two features/buttons from the main UI that i was using all the time:
nb: That Apply button was moved to the Style Editor, but i think it's unintuitive because if does pick the style(s) selected in the main UI instead of from the style editor. Would be nice if it's considered bringing them back where they were, in fact the toprow does now look rather empty with just two buttons so space should not be of concern and it will look more feature-rich again :) /cc @AUTOMATIC1111 |
I agree it's unintuitive but voldy said he doesn't want to put the buttons in the main UI since it's limited on space. (You can see what he's referring to in my PR here: #12322) |
Yeah, I realize that too. The problem is how the styles UI is created within the code itself now. It's basically forced into the same row as the dropdown. Myself, or someone else if I don't get to it, can try taking a look into it later. I'd say it's a bit low priority right now though since the functionality does work, even if a bit obtuse now. |
Is your feature request related to a problem? Please describe.
Lots of styles (60 for me) are hard to track or manage in the pulldown list.
Describe the solution you'd like
A style manager. Allowing deleting and sorting styles in the webui.
Even better if creation time, comments and insertion/deletion comparing are supported.
Describe alternatives you've considered
Editing styles.csv. Have to leave the webui.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: