Skip to content
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

Buttons to select sub-folders for models (lobe theme support) #319

Closed
1 task done
LindezaBlue opened this issue Feb 18, 2024 · 4 comments
Closed
1 task done

Buttons to select sub-folders for models (lobe theme support) #319

LindezaBlue opened this issue Feb 18, 2024 · 4 comments
Labels
enhancement New feature or request

Comments

@LindezaBlue
Copy link

Is there an existing issue for this?

  • I have searched the existing issues and checked the recent builds/commits

What would your feature do ?

I have noticed that in the Forge webui the folder buttons are missing when using the Lobe Theme extension. This is already in the A1111 original program so I am not sure why it isn't in forge.

Forge Interface:

image

A1111 Interface:

image

It's a simple feature, and I am not sure if it is a bug or intentional... but I really like the ability to find models quickly with these buttons than scrolling through literally hundreds of models.

Thank you for making a wonderful version of webui it works amazing, and I can't wait to see how it grows. <3

Proposed workflow

  1. Open Extra Networks folder while using the Lobe Theme
  2. Make sure the models are sorted within sub-folders so the folders show up in the Extra Networks tab
  3. See above photos for reference

Additional information

NA

@LindezaBlue LindezaBlue added the enhancement New feature or request label Feb 18, 2024
@catboxanon
Copy link
Collaborator

This is intentional as the buttons were replaced with a tree view in the dev branch a month ago. AUTOMATIC1111/stable-diffusion-webui#14588

I would open an issue in the lobe theme repo to add proper support for this. Closing.

@LindezaBlue
Copy link
Author

LindezaBlue commented Feb 19, 2024

Well that didn't answer my question, since I have the most recent version of A1111 currently and it works on the latest build of A1111.

@catboxanon I feel that was a bit quick on your part to close this post, and for posting an answer without first asking for more information as to what build I am currently using for A1111, or anything else for that matter is a bit rude. Some confirmation or communication would have been nice at the very least. I am not trying to start a fight or anything, but some common courtesy would have been nice.

Just so we are all on the same page, I am using A1111 release version 1.7.0 and have access to these buttons in the latest build of A1111.
If as the devs of Forge claim, "Forge promise that we will only do our jobs. Forge will never add unnecessary opinioned changes to the user interface. You are still using 100% Automatic1111 WebUI."
and it indeed is the same interface as A1111, that would not explain why the buttons are missing since the features would be identical minus the backend that is related to optimizations.

Also both installations have the new "tree view" in the settings. I double checked to make sure they both had it.
So to say that the tree view or an outdated version is being used is the issue, I feel is incorrect.

Maybe someone that actually works on programming Forge's software could chime in and give a better answer instead of copy pasting a post from another programs build?

Thanks!

@catboxanon
Copy link
Collaborator

Forge is based on the dev branch, or rather the newly released 1.8.0 RC, whereas 1.7.0 is months older. 1.7.0 also does not have a tree view as that was only merged into dev (1.8.0) a month ago, and is also what removed those folder buttons. AUTOMATIC1111/stable-diffusion-webui#14588

Feel free to re-open this issue if you don't think it's been resolved.

@LindezaBlue
Copy link
Author

LindezaBlue commented Feb 19, 2024

Huh weird, I do have the settings for tree view in 1.7.0 so I'm not sure why that's there if it's only in the dev branch ver 1.8.0... I'm gonna go try and do more testing to see if I can find a workaround in the meantime.

Thank you for the clarification. That does explain thing a little better. I'll post about this over in Lobe and see what they come up with for the dev branch version.

Thank you again for helping!~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants