Environment
- Operating system: Debian Testing
- Hyperkeys version: 1.3.1
Describe the bug and how to reproduce
If I add "Run command" and click the gear settings, the window becomes a blank gray and I can't do anything until I restart the application.
If I add "Switch audio output", and set it to a shortcut, nothing seems to happen.
Expected behavior
I was expecting to be able to configure a command or a soundcard to switch to. As far as linux goes, is there any advantage to HyperKeys over the standard Keyboard Shortcuts app? Maybe the primary users are on Windows?
Config file
[{"name":"RUN_COMMAND","shortcuts":{"RUN_COMMAND":"ctrl+*"},"config":{"command":""},"id":"21cfa819-f07b-4298-8bf1-2466019f04ae","enabled":true},{"name":"SWITCH_AUDIO","shortcuts":{"SWITCH_AUDIO":"ctrl+/"},"id":"fff17893-779e-492f-8b5e-4b72bcaa50df","enabled":true}]
Screenshots

Clicked on the gear:

Environment
Describe the bug and how to reproduce
If I add "Run command" and click the gear settings, the window becomes a blank gray and I can't do anything until I restart the application.
If I add "Switch audio output", and set it to a shortcut, nothing seems to happen.
Expected behavior
I was expecting to be able to configure a command or a soundcard to switch to. As far as linux goes, is there any advantage to HyperKeys over the standard Keyboard Shortcuts app? Maybe the primary users are on Windows?
Config file
[{"name":"RUN_COMMAND","shortcuts":{"RUN_COMMAND":"ctrl+*"},"config":{"command":""},"id":"21cfa819-f07b-4298-8bf1-2466019f04ae","enabled":true},{"name":"SWITCH_AUDIO","shortcuts":{"SWITCH_AUDIO":"ctrl+/"},"id":"fff17893-779e-492f-8b5e-4b72bcaa50df","enabled":true}]
Screenshots
Clicked on the gear: