Desktop App: Global shortcut has to be typed out
rick-urb opened this issue · comments
On the Desktop App, when setting a global shortcut, the shortcut has to be literally typed out, instead of just pressing the keys for the shortcut.
A bit clumsy.
Auto-recognition of those keys would be much better, or at least, a little note letting users know that they have to type "CTRL+...".
This issue already existed in the previous version. When using the application for the first time, it is not clear that the shortcut must be entered manually. This only becomes apparent after several attempts through trial and error.
I kind of like it that way, but I'm a weirdo who mapped my hotkey to F24, which does not exist on my actual keyboard.
This issue already existed in the previous version. When using the application for the first time, it is not clear that the shortcut must be entered manually. This only becomes apparent after several attempts through trial and error.
This is NOT an issue this definitely a feature -
As explained by @swimJim for some automation you may want to map some hotkey to key that does not exist on your keyboard and you cannot do that if you have to activate a keyboard key but you always can type yourself any keyboard key definition you want so it's definitely an advanced feature and all hotkey in every software should work like that
I would suggest that @braden-w close this "issue".
@OLH21 – still, it should be clarified via a note or popup, since your average user won't know that it has to be typed out.
This is NOT an issue this definitely a feature -
As explained by @swimJim for some automation you may want to map some hotkey to key that does not exist on your keyboard and you cannot do that if you have to activate a keyboard key but you always can type yourself any keyboard key definition you want
The manual entry itself is not the issue, and I understand why it makes sense.
However, the lack of clarity is problematic. Users typically attempt to input shortcuts using key combinations as they would in other applications, but this doesn't work here.
What's missing is a clear indication that the shortcut needs to be manually typed in. Without this guidance, users can only figure it out through trial and error, which can be frustrating. A simple hint or instruction about the need for manual shortcut entry would greatly improve the user experience and prevent confusion.
Hey guys, thank you for all the discourse and comments here. I'm currently limited by the Tauri global keyboard shortcut API, and so I unfortunately have to register shortcuts with text.
However, I do plan on working on some sort of keyboard registration flow in the future!
This is NOT an issue this definitely a feature -
No worries, in GitHub both issues and features go under issues 😄