[GH-ISSUE #116] It cannot be used without loading settings_interface #87

New issue

Closed

opened 2026-10-30 21:18:50 +00:00 by bsakaguchi · 4 comments

bsakaguchi commented

2026-10-30 21:18:50 +00:00

Owner

Originally created by @JLWLL on GitHub (Jan 23, 2023).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/116

Originally assigned to: @DominikDoom on GitHub.

IF I comment this line
IN webui modules/ui.py line 1765
tagcomplete cannot work.

# interfaces += [(settings_interface, "Settings", "settings")]

Is it a bug or an optimization?
I want to using it without settings_interface
Thanks.

Originally created by @JLWLL on GitHub (Jan 23, 2023). Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/116 Originally assigned to: @DominikDoom on GitHub. IF I comment this line IN webui modules/ui.py line 1765 tagcomplete cannot work. `# interfaces += [(settings_interface, "Settings", "settings")]` ![image](https://user-images.githubusercontent.com/86763551/213995661-00035274-528d-437d-822c-6e4727f56eac.png) Is it a bug or an optimization? I want to using it without settings_interface Thanks.

bsakaguchi

2026-10-30 21:18:50 +00:00

closed this issue
added the
bug
label

bsakaguchi commented

2026-10-30 21:18:51 +00:00

Author

Owner

@DominikDoom commented on GitHub (Jan 23, 2023):

The extension currently needs the settings interface since it watches / reacts to changes to the autocomplete related settings. I didn't consider that some might not use the settings interface, I can have a look at making it work without it later.

Just some small addendum: If you just want to prevent setting changes on a shared instance or similar, you can use the --freeze-settings command line argument when launching the webui instead of commenting out the line. In that case the extension should already work.

@DominikDoom commented on GitHub (Jan 23, 2023): The extension currently needs the settings interface since it watches / reacts to changes to the autocomplete related settings. I didn't consider that some might not use the settings interface, I can have a look at making it work without it later. Just some small addendum: If you just want to prevent setting changes on a shared instance or similar, you can use the `--freeze-settings` command line argument when launching the webui instead of commenting out the line. In that case the extension should already work.

bsakaguchi commented

2026-10-30 21:18:51 +00:00

Author

Owner

@JLWLL commented on GitHub (Jan 23, 2023):

The extension currently needs the settings interface since it watches / reacts to changes to the autocomplete related settings. I didn't consider that some might not use the settings interface, I can have a look at making it work without it later.

Just some small addendum: If you just want to prevent setting changes on a shared instance or similar, you can use the --freeze-settings command line argument when launching the webui instead of commenting out the line. In that case the extension should already work.

Thanks for your reply.
As you said, I will share the instance with others, and I don't want them to change some of the Settings, so my previous practice was comments.
--freeze-settings still displays the Settings interface after use, this is not good, for the front interface is not very beautiful, hope you can fix. Thank you very much!

@JLWLL commented on GitHub (Jan 23, 2023): > The extension currently needs the settings interface since it watches / reacts to changes to the autocomplete related settings. I didn't consider that some might not use the settings interface, I can have a look at making it work without it later. > > Just some small addendum: If you just want to prevent setting changes on a shared instance or similar, you can use the `--freeze-settings` command line argument when launching the webui instead of commenting out the line. In that case the extension should already work. Thanks for your reply. As you said, I will share the instance with others, and I don't want them to change some of the Settings, so my previous practice was comments. `--freeze-settings` still displays the Settings interface after use, this is not good, for the front interface is not very beautiful, hope you can fix. Thank you very much!

bsakaguchi commented

2026-10-30 21:18:51 +00:00

Author

Owner

@DominikDoom commented on GitHub (Jan 24, 2023):

I have added some safety checks to skip listeners if the settings are missing.
One thing to note is that it will still work with anything you've added to the quicksettings bar, since that isn't reliant on the settings tab itself.

@DominikDoom commented on GitHub (Jan 24, 2023): I have added some safety checks to skip listeners if the settings are missing. One thing to note is that it will still work with anything you've added to the quicksettings bar, since that isn't reliant on the settings tab itself.

bsakaguchi commented

2026-10-30 21:18:52 +00:00

Author

Owner

@JLWLL commented on GitHub (Jan 24, 2023):

I have added some safety checks to skip listeners if the settings are missing. One thing to note is that it will still work with anything you've added to the quicksettings bar, since that isn't reliant on the settings tab itself.

It work！！！！！
Thank you very much！！！

@JLWLL commented on GitHub (Jan 24, 2023): > I have added some safety checks to skip listeners if the settings are missing. One thing to note is that it will still work with anything you've added to the quicksettings bar, since that isn't reliant on the settings tab itself. It work！！！！！ Thank you very much！！！