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
When working with config sets, pressing CMD+B to jump to the base set is very convenient. It would be even more convenient if there was a fast way to jump to any config set, but we can't realistically assign keyboard shortcuts to everything. Instead, a quick switch command should be added. The user would do something - for the sake of discussion let's say CMD+L - and could immediately type info a field, ideally with autocomplete, press return and jump to whatever was typed. So if the user has a "Ragnarok" config set, they might press CMD+L, type "rag", press something like tab to accept the autocomplete, and then return. The config set would be switched to without the keyboard required at all.
In theory, this could be expanded beyond config sets. Maybe the user could start typing the name of a config they are looking for, in either english or official key, and Beacon could jump right to that editor and put the focus on the field?
The text was updated successfully, but these errors were encountered:
I think there is one specific use case that could use it's own shortcut: open previous set. This could easily allow to jump between two sets for example to compare settings (like setting up an event's config)
When working with config sets, pressing CMD+B to jump to the base set is very convenient. It would be even more convenient if there was a fast way to jump to any config set, but we can't realistically assign keyboard shortcuts to everything. Instead, a quick switch command should be added. The user would do something - for the sake of discussion let's say CMD+L - and could immediately type info a field, ideally with autocomplete, press return and jump to whatever was typed. So if the user has a "Ragnarok" config set, they might press CMD+L, type "rag", press something like tab to accept the autocomplete, and then return. The config set would be switched to without the keyboard required at all.
In theory, this could be expanded beyond config sets. Maybe the user could start typing the name of a config they are looking for, in either english or official key, and Beacon could jump right to that editor and put the focus on the field?
The text was updated successfully, but these errors were encountered: