-
-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Turbo-Mode for shortcuts without modifiers #407
Comments
Hi there! I totally understand your point (I also use Turbo mode more or less exclusively). Here are some thoughts from my side:
So I think that there are at least two alternative solutions to your issue:
|
|
Yeah, I just mean "any key is currently pressed on the keyboard". That means if you press F1 and keep it pressed, the menu is in Turbo-Mode until you release the key. This would require no additional setting. However, I am not sure if this is possible. I'll give this a test. And Hover mode will come back as well, however this will be tracked in #303. |
Currently the default Kando shortcut (ex.Ctrl+Space) opens the menu in Point-and-Click mode but while you hold the associated modifier (ex.Ctrl) you switch to Turbo-Mode. I prefer Turbo-Mode to the point that it's the only mode I would like to use, however, I would also like to activate it with just one key button (ex. F1). That is not currently possible because Turbo-Mode's activation is associated with the Point-and-Click mode modifier.
My initial implementation suggestion would have been:
In the json settings this could be under the "shortcut" section called something like "shortcutTurbo"
My more complicated implementation suggestion is:
The same as above. However, instead of "shortcut" and "shortcutTurbo" you would have something like "primaryShortcut" and "secondaryShortcut" with the option of making Turbo-Mode as the "primaryShortcut". Why? Well this makes it so that if you want to primarily use Turbo-Mode, you don't have to manually set 2 shortcuts every time you make a menu.
I would honestly be more than happy with just the initial implementation, especially since I have no clue what the general activation type preferences are for Kando users.
The text was updated successfully, but these errors were encountered: