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

Bug on enqueue button placement #228

Open
zxt57 opened this issue Mar 15, 2024 · 1 comment
Open

Bug on enqueue button placement #228

zxt57 opened this issue Mar 15, 2024 · 1 comment

Comments

@zxt57
Copy link

zxt57 commented Mar 15, 2024

Hi,

With the latest update, the function after_component is taking account of shared.opts.compact_prompt_box, if it's true then the option queue_button_placement is ignored and the enqueue button will always be placed under the generate_box.

I dont see why placing the button under the generate button would be a viable option, because when generating in the a1111 webui, the generate button will change (to interrupt|skip) and the enqueue button will also be hidden, which defeat the whole purpose of this extension.

Maybe it's better to place the button one level higher or dont ignore the option shared.opts.queue_button_placement ?

Thanks,

@Mark-Reiser
Copy link

I guess I am experiencing the same issues with the "enqueue" button.

Often it´s unresponsive from the beginning -- only a browser ui refresh helps.
But whats worse is that is even more likely unresponsive while a job is already running -- and that´s what the other commenter said "defeats the whole purpose of this extension".

Please fix! This great extension is SO MUCH valueable for my work with SD!

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

No branches or pull requests

2 participants