[BUG] Changing the Handy shortcut from ctrl + space doesn't work.
Bug Description
Whenever I try to change the Handy shortcut from ctrl + space, it doesn't work for many other keys or key combinations. Some combinations, like shift + ctrl, immediately revert back to ctrl + space in the GUI, while others like my preferred shortcut (scroll lock) disappear after restarting Handy (and don't work even before the restart, even though the GUI lists it as the shortcut).
My preference would be to be able to press scroll lock to start transcription, then press it again to stop.
System Information
App Version: v0.3.8
Operating System: Windows 10
CPU: Intel i7-7700K
GPU: NVIDIA GeForce RTX 3060
Let me see if I can replicate on Windows. I'm gone for a few days but will try it. This issue has been reported before and I haven't been able to replicate for the fix
I just installed Handy 0.4.2 and couldn't even figure out how to define the shortcut. It wasn't until I came here and searched for Windows that I found that Control Space is the default. In fact it says that there's no shortcuts defined. However, I'm happy to say that Control Space does work. In fact, I typed out this issue using it.
Oh thank you for this note, are you on Windows 10? I'll try to fix that bug with no shortcut defined, that's really not right
I am using Windows 11 Pro.
Thanks, this is a big issue, I'll try to replicate and fix.
Oh thank you for this note, are you on Windows 10? I'll try to fix that bug with no shortcut defined, that's really not right
I'm seeing the same thing ("No shortcuts configured") with no way to configure a shortcut. Windows 10 Pro
Edit: As an aside, I was able to get the transcription working using the control space shortcut. That portion actually does work really well, and I'm excited to keep using it.
Thanks for the additional report @therealpygon! Hopefully, within the next week, I'll be able to test Windows and fix this. I suspect that this is a bug with something, how I configured the settings, and I refactored it in the latest version and probably this is a bug as a result of that, so hopefully I'll be able to get that fixed at the very least.
Similar problem I have on Apple Silicon. most text to speech apps on Apple use the Fn as hotkey. But I am not able to switch it to this one. It always gets back to the standard.
See #134.
I was able to change the hotkey in the current release (0.5.1) so this issue can be closed @cjpais
@BrianGilbert what OS are you on?
@cjpais MacOS Tahoe (M1 Apple sillicon), I can test on Windows 11 as well later today
If you could that'd be great but I do think largely this might be around Windows 10 or specific configurations. On the whole it does work but some certain configurations it fails for some reason
This is a bit strange but the shortcut now shows up for me and I'm still using 0.4.2. I've attached the same screenshot as before but this time you can see the option to pick the shortcut. I hope it wasn't a transient Windows error on my side. Thanks all the same for the support.
I have some ideas why that might be too, I'll try and test when I can and see if it shows up
I'd love to be able to use a single key hotkey as well, e.g right command or right option on mac. As of now, the app seems to only support a key combination instead of a single key. @cjpais any thought?
@hoangtrann see other issues where this is discussed as well as 2 open PRs
I'd love to be able to use a single key hotkey as well, e.g right command or right option on mac. As of now, the app seems to only support a key combination instead of a single key. @cjpais any thought?
YES THIS --> 💯% I was just about to open another issue, I want this exactly:
- Push to talk: hold
fnkey (only)
(btw I have tried unsetting that from Wispr Flow to free up the space for use the fn key but didn't help.
Hi guys, Win 10 pro. Can confirm that this is a mess, even more on azerty keyboards.
| Just holding... | ...shows... | ...and gives... | (screenshot) |
|---|---|---|---|
| function | wakeup | nothing | |
| ctrl+w | ctrl+z | ctrl+z | |
| ctrl+z | ctrl+w | ctrl+w | |
| fn+x | wakeup+x | nothing | |
| < | intlbackslash | nothing | |
| ctrl+< | intlbackslash | nothing |
Some combinations that work:
- ctrl+space
- alt+[letter]
So basically my conclusions are:
- special characters and keys are messed up
- the app thinks qwerty while configuring the shortcuts, but properly thinks azerty while using the shortcut
Anyway, thanks a lot for the great app!
Definitely! Would love any help on this issue I definitely think it's solvable
I am planning a refactor already for the keyboard generally but I'm happy to accept any reasonable PR which fixed this issue
Would love any help on this issue I definitely think it's solvable
I'd love to help on the code, but alas it's not in my skillset. :/ But I can help to test though, if need be.