Instead of commands in the search bar, provide interface controls (button, drop-down list, input field, check box)

[Raindrops]

It is hard for an average user to know (or remember) various configuration-related commands like About:keys.
Instead, such commands should be converted into interface control (button, drop-down list, input field, check box, etc.)

For example, instead of the about:keys command, a button should be provided as follows:

View all hotkeys.png (36.93 KiB) Viewed 10829 times

[void]

about:keys is currently a hidden advanced feature.

I am considering an about:keys link under Tools -> Options -> Keyboard.

Thank you for the suggestion.



I have on my TODO list to show the key bindings in the main list.

[Raindrops]

Thank you!

Another idea is to let the user search for a particular hotkey in this window itself.

Imagine this scenario:
1. User clicks in an input field, and presses a hotkey (e.g. CTRL+SHFT+SpaceBar).
2. The field shows all functions that are bound to this hotkey.

This will make it easy to find any problematic hotkey.

In other words, currently the interface shows all hotkeys bound to a give menu item.
In addition to that, we should have the reverse relationship (find all commands bound to the hotkey in different modes.)

Currently, we have to first launch the about:keys and then search in that text file by typing the spelling of the desired hotkey.
But this can be difficult to use, because we have to use the exact spelling that used in Everything.
There are many other popular spellings for keys. But searching for them would fail to find them.

For example, typing SHFT, BKSP, UpArrow, etc. will fail to find any result.

[void]

I will consider searching for the hotkey from the search box.

Thank you for the suggestion.

[Thy Grand Voidinesss]

These ideas are legit thus I await for their implementation
AKA
+ 1