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
Love the new styles feature from #196 . The rate of development on this repo is unbelievably impressive.
There ought to be a button that lets us delete an existing preset, or better yet, an area to modify the title and contents. Also, presets may become more sophisticated in the future, housing additional settings such as denoise strength... it might make sense to have "Style Manager" as a standalone tab in the UI so as not to clutter the rest of the app.
For anyone wondering, you can manage your styles manually through "styles.csv" in the root directory of the webui.
I wouldn't be surprised if this is already on the roadmap, but I figured I'd mention it just in case. Thanks!
The text was updated successfully, but these errors were encountered:
But hey, if you know anything about IOComponents, can you help get some unique parameter pushed through the kwargs for after_component and before_component, so I can identify which script the component is for, without having to rely lables and element id's. I haven't implemented element id's yet, as I have been drilling through the main code, to see if I can find a way to do just that.
Love the new styles feature from #196 . The rate of development on this repo is unbelievably impressive.
There ought to be a button that lets us delete an existing preset, or better yet, an area to modify the title and contents. Also, presets may become more sophisticated in the future, housing additional settings such as denoise strength... it might make sense to have "Style Manager" as a standalone tab in the UI so as not to clutter the rest of the app.
For anyone wondering, you can manage your styles manually through "styles.csv" in the root directory of the webui.
I wouldn't be surprised if this is already on the roadmap, but I figured I'd mention it just in case. Thanks!
The text was updated successfully, but these errors were encountered: