-
-
Notifications
You must be signed in to change notification settings - Fork 179
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
Unable to set shortcut #241
Comments
Hello @Techassi Can you try with a different function key ? It's possible this shortcut is already used by another application (I know Intel Graphic Utility bind a lot of the CTRL+ALT+FX) |
Hey @Belphemur I tried many different combinations, e.g.:
I tried |
Usually it means it couldn't register the hot keys.
Try something like CTRL+ALT+5 (like numlock 5) to see if it lets you do
that.
…On Fri, 2018-03-02 at 08:05 -0800, Sascha L. wrote:
Hey @Belphemur
I tried many different combinations, e.g.:
CTRL+FX
SHIFT+FX
ALT+FX
I triedF1, F2, etc for each combination from above. One more thing:
the font color turns red (I guess because my shortcut is incomplete)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c5
5493e4bb","name":"GitHub"},"entity":{"external_key":"github/Belphemur
/SoundSwitch","title":"Belphemur/SoundSwitch","subtitle":"GitHub
repository","main_image_url":"https://cloud.githubusercontent.com/ass
ets/143418/17495839/a5054eac-5d88-11e6-95fc-
7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent
.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-
b52498112777.png","action":{"name":"Open in GitHub","url":"https://gi
thub.com/Belphemur/SoundSwitch"}},"updates":{"snippets":[{"icon":"PER
***@***.*** in #241: Hey @Belphemur \r\n\r\nI tried
many different combinations, e.g.:\r\n- `CTRL+FX`\r\n-
`SHIFT+FX`\r\n- `ALT+FX`\r\n\r\nI tried` F1`, `F2`, etc for each
combination from above. One more thing: the font color turns red (I
guess because my shortcut is incomplete)"}],"action":{"name":"View
Issue","url":"#241 (comment)
uecomment-369965197"}}}
|
Ok I will try you suggestion and will report back! |
@Belphemur Why is there |
If you check the mails sent by GitHub, you'll see this JSON in all of
them.
It's the inbox markup for having direct action in Gmail/Inbox.
The API_KEY doesn't belong to me.
…On Sun, 2018-03-04 at 11:14 +0000, Technetium wrote:
@Belphemur Why is there api_key in your comment footer above? 😲
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c5
5493e4bb","name":"GitHub"},"entity":{"external_key":"github/Belphemur
/SoundSwitch","title":"Belphemur/SoundSwitch","subtitle":"GitHub
repository","main_image_url":"https://cloud.githubusercontent.com/ass
ets/143418/17495839/a5054eac-5d88-11e6-95fc-
7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent
.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-
b52498112777.png","action":{"name":"Open in GitHub","url":"https://gi
thub.com/Belphemur/SoundSwitch"}},"updates":{"snippets":[{"icon":"PER
***@***.*** in #241: @Belphemur Why is there
`api_key` in your [comment](https://github.com/Belphemur/SoundSwitch/
issues/241#issuecomment-369966817) footer above?
😲\r\n"}],"action":{"name":"View Issue","url":"https://github.com/Bel
phemur/SoundSwitch/issues/241#issuecomment-370220732"}}}
|
I now tried to set my shortcut to something like Marking this issue as closed. |
Same issue here, but the PC was put to suspend several times. |
Running into the same issue. Any hotkey combination results in a red font, but a reboot seems to solve the issue. |
Hi SoundSwitch Team,
I recently switched to a new PC and installed SoundSwitch. I wanted to use my old shortcut, so I tried to set it.
My preferred shortcut is:
CTRL+ALT+F3
SoundSwitch turns that into:
CTRL+ALT+
It won't let me insert the
F3
part.Additional information:
The text was updated successfully, but these errors were encountered: