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
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
As it stands it seems that pressing a key-binding whilst using the resolver still executes the associated command for that binding. Wouldn't it be better if the actual execution of a given command was blocked whilst the keybinding resolver is active? So just the information for a particular key combination is given, but no actions are taken at that stage.
I've had some pretty inconvenient commands be activated whilst just quickly needing to look at what command (if any) is on a particular key combination. Would it not make sense to have the opportunity to decide whether or not to actually use that command only after getting to see what it is?
The text was updated successfully, but these errors were encountered:
Yes just came back to edit, to say that maybe an optimal solution would actually be to have a toggle button on the keybinding resolver UI (I guess similar to the find/replace UI toggles) to switch between active/non-active mode. Giving greater flexibility than say an option in the package settings?
As it stands it seems that pressing a key-binding whilst using the resolver still executes the associated command for that binding. Wouldn't it be better if the actual execution of a given command was blocked whilst the keybinding resolver is active? So just the information for a particular key combination is given, but no actions are taken at that stage.
I've had some pretty inconvenient commands be activated whilst just quickly needing to look at what command (if any) is on a particular key combination. Would it not make sense to have the opportunity to decide whether or not to actually use that command only after getting to see what it is?
The text was updated successfully, but these errors were encountered: