mirror of
https://github.com/DominikDoom/a1111-sd-webui-tagcomplete.git
synced 2026-11-05 00:17:25 +00:00
[GH-ISSUE #127] [Request] Toggle or customize keys for navigating list #91
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
low priority
low priority
pull-request
question
waiting for feedback
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
DominikDoom/a1111-sd-webui-tagcomplete#91
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TFWol on GitHub (Feb 17, 2023).
Original GitHub issue: https://github.com/DominikDoom/a1111-sd-webui-tagcomplete/issues/127
Originally assigned to: @DominikDoom on GitHub.
After updates, I usually go in and edit the script to remove capturing of Home and End keys since I use those to jump around the prompt as things pop up in my mind.
Here:
github.com/DominikDoom/a1111-sd-webui-tagcomplete@c1fb4619a4/javascript/tagAutocomplete.js (L688)Would you consider adding a way to choose the desired key or at least toggling it off/on?
I'd use the blacklist, but that disables the list entirely rather than just a couple of keys.
Editing the file is not too much of a hassle, but I'd thought I'd ask.
@DominikDoom commented on GitHub (Feb 18, 2023):
Custom keys would have to be done by editing a local file (since I really don't want to bother with a custom UI or using the limited gradio settings inputs for it), which I guess would be feasible since they aren't likely changing much in the future.
I never really saw the need for it, since you just have to press Escape to close the autocomplete window if you want to jump in the text without completing something, which will make the following inputs behave normally again. But I understand it can be annoying due to muscle memory, so really I'll just add it now since it won't hinder anyone. And more customizability is always nice!
@DominikDoom commented on GitHub (Feb 18, 2023):
I've added the custom key bindings feature, you can adjust them by editing the new
keymap.jsonfile in the extension's tags folder. So you can either set the bindings currently using Home/End to something else or disable them entirely by setting them to "None" or leaving the string empty.@TFWol commented on GitHub (Feb 19, 2023):
Works wonderfully, thanks!
@Kenqr commented on GitHub (Apr 3, 2023):
The keymap.json file gets reset every time the extension is updated. Is there any way to keep my settings after updates?
@DominikDoom commented on GitHub (Apr 3, 2023):
@Kenqr It seems the webui changed the update mechanism quite a while ago already from just git pull to a rebase, which removes local changes even if the file didn't change upstream. I wasn't aware of that, I will try to migrate the key map to the normal Gradio settings in a sensible way.
@DominikDoom commented on GitHub (Apr 3, 2023):
@Kenqr I was able to add it successfully, you can now just edit the hotkeys (and colors) in the webui settings page. As long as you don't break the JSON in the textbox it will work the same as before.
@Kenqr commented on GitHub (Apr 3, 2023):
Wow, that was fast.
Thanks!