Unexpected behaviors in keyboard shortcut config in Windows

A couple of unexpected behaviors when trying to configure my shortucts in the Windows app:

• The keys show up as Mac keys (command, option, etc). I couldn’t find a setting to change them but then again, this is a Windows app, they should be Windows keys by default, no?

• I set up the transcription hotkey shortcut (ctrl+Win). Then I wanted to set Ctrl+Win+Space as my hands-free shortcut, emulating what I had in Wispr Flow. But when I press the combination to try to set the hands-free, since it´s already assigned to the transcription shortcut, it will activate the transcription and when I let go, it adds (Command + V) to the shortcut.

• After some fiddling around I discovered that I can press the keys one by one and build the shortcut that way, which worked, but it wasn’t my first thought to do it like that and I´m pretty sure for most apps you just press the combination of keys as you would when activating the shortcut.

• Even after setting the shorcuts the way I wanted, they don´t work as expected or as they do in Wispr Flow which I found super useful, this would be a nice addition!
  1. You press Ctrl+Win to activate transcription
  2. While those are held down, you can hit spacebar to “lock” it into hands-free mode
  3. If you’re holding down Ctrl+Win after some time (it’s probably like 10 seconds or so) it will show a small message above the audio waveform indicator suggesting that you can press spacebar to lock it into hands-free mode.