Open JB-DX opened 10 months ago
I'm not sure there was any change in this regard in Open-Shell
. So it should behave just as Classic-Shell
did.
Not sure what menu style you are using. Though all except for Classic style
have search box active when Win key is pressed. Thus any key presses go to search box.
You can disable that by looking for Show search box
setting and selecting either No search box
or Access with Tab
.
After that keyboard shortcuts should work normally.
Sorry I forgot to say that I'm using Classic style. I just tried the other styles, that allow a search. But that is even worse, it requires more key strokes, and my 'e' example does not work at all, as everything.exe does not show up at all. So the simple straightforward 2-keystroke behavior of classic-shell is missing.
Is your feature request related to a problem? Please describe.
With Classic Shell I could quickly start a program like Everything.exe by pressing Win-Key and then the 'E'-key. Doing the same with Openshell it jumps down to "Einstellungen" (German for Settings) and ignores the Everything-Icon. Only characters not assigned to fixed functions allow the fast-start, like '1' for an icon starting with '1' I found no setting to get the Classic-Shell behavior back. If there is one, please point me to that.
Describe the solution you'd like
Pressing the Win-key followed by a 'a'-'z' or '0'-'9' key should immediately start a program when an icon exist starting with that character. If there are several icons having the same start-character, then the first icon should get highlighted, when pressing the same key again the highlight should move to the next icon having the same first letter. Pressing the return-key at each stage will launch the program. For the 'e'-key example in above, the highlight will eventually end up at "Einstellungen" and then move back to the first entry with 'e' again when pressing the e-key again. This behavior is identical to Classic-Shell.
Area of issue
Start menu
Alternatives you've considered
No response
Additional context
No response