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
Version 9 of Foundry has a registration system for key bindings. This issue tracks the possible integrations that will allow quicker navigation of the quest log.
One area that I'll be looking into bindings for is the main quest log UI. IE bindings to move quests between categories and / or deleting quests.
I welcome any other ideas / suggestions on UX / user experience patterns that can benefit from key bindings.
The text was updated successfully, but these errors were encountered:
Indeed... open & close of the quest log / quest tracker as two essential / main bindings makes sense.
I'm also curious about workflows inside of the quest log. I think in general some of the most relevant key bindings like opening the log / tracker will make the first release of TQL. These two seem like the only real external key bindings to register.
A bit of research is in order too. Given the new tech stack for the UI layer it might be possible to engage a local key binding system when the quest log is the focused / selected app. This opens up a lot of possibilities for advanced workflows inside the quest log itself.
Version 9 of Foundry has a registration system for key bindings. This issue tracks the possible integrations that will allow quicker navigation of the quest log.
One area that I'll be looking into bindings for is the main quest log UI. IE bindings to move quests between categories and / or deleting quests.
I welcome any other ideas / suggestions on UX / user experience patterns that can benefit from key bindings.
The text was updated successfully, but these errors were encountered: