You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Regularly CAPS LOCK is the default key binding for broadcasting. In the past I had troubles with this, belonging to a windows keyboard setting, that I had to press CAPS LOCK again, after broadcast was finished to unlock CAPS LOCK and just then pressing CAPS LOCK another time, I could braodcast again.
Pressing CAPS LOCK - locked (lamp on) - broadcasting
Pressing CAPS LOCK - unlocked (lamp off) - not broadcasting
I could figure out how to change the corresponding setting in the windows environment. But now it hits me again.
The change I found does not turn off CAPS LOCK after releasing CL-key, it just offers the possibilty to press it and broadcast another message. So CAPS LOCK is still locked after every second broadcast. AS long as CL is locked, all other key combinations for example CTRL + arrow_down accidently hits CTRL + SHIFT + arrow_down, since CL in fact is a temporary SHIFT without the need to hold that key down.
So it'd be a huge advantage if activated CAPS LOCK is automatically unlocked after key was released.
The text was updated successfully, but these errors were encountered:
The simple solution for this would be to just move the default keybind to another key. While I understand the convenience of CAPS LOCK in terms of its location, it being used as a keybind is always connected to some sort of downside.
Regularly CAPS LOCK is the default key binding for broadcasting. In the past I had troubles with this, belonging to a windows keyboard setting, that I had to press CAPS LOCK again, after broadcast was finished to unlock CAPS LOCK and just then pressing CAPS LOCK another time, I could braodcast again.
Pressing CAPS LOCK - locked (lamp on) - broadcasting
Pressing CAPS LOCK - unlocked (lamp off) - not broadcasting
I could figure out how to change the corresponding setting in the windows environment. But now it hits me again.
The change I found does not turn off CAPS LOCK after releasing CL-key, it just offers the possibilty to press it and broadcast another message. So CAPS LOCK is still locked after every second broadcast. AS long as CL is locked, all other key combinations for example CTRL + arrow_down accidently hits CTRL + SHIFT + arrow_down, since CL in fact is a temporary SHIFT without the need to hold that key down.
So it'd be a huge advantage if activated CAPS LOCK is automatically unlocked after key was released.
The text was updated successfully, but these errors were encountered: