Caps Lock (HOLD) instead of (TOGGLE) or (HOLD) function for normally toggled keys.

[Doubs115]

Is your feature request related to a problem? Please describe. I used to use AHK to use my caps lock like a shift key as I don't really see a reason for it when you know how to type fast or properly. Furthermore, in games I tend to hate when I am trying to type something and realize I bumped, more likely I often use caps as my map, crafting or inventory depending on the game. This results in me trying to use a map, then going to type and it sounding like I am screaming.

Describe the solution you'd like Allow some sort of switch for toggle keys to be used as normal hold keys. As in Press's down on caps enters the "On" state. Releases the key returns to the "Off" state, like a normal WASD in games. This switch could either be located as part of the existing DKS (see more below) or maybe a sub menu of the key remapping section or even individual "New" keys. This might also allow even more button combo's for macros etc. Describe alternatives or workarounds you've considered As mentioned before an alternative is AHK, it works but has issues with anti-cheats and is another program on sometimes bloated systems. Something I have also tried is the DKS function. The problem I face when using this is for some reason even if the key is fully held down, games only see it as a press and release of around 20-30ms and not a constant (HOLD) despite the LED showing a constant (HOLD).

Additional context I currently know of 2 ways of using DKS: the first is listed above, the second way I will try my best to explain. I don't remember how but because of the issue above it would almost press the caps key 3-4 times instead of 1-2. I would press down and the map would flash, go away, then become constant. This behavior worked for all games but also has issues like inconsistent mouse movement across some games when holding for a map aka stuttering for only the mouse. My theory is maybe because in reality the map screen is actually flashing really fast but doesn't look like it visually, that being said that theory has flaws because that theoretically would always reset the mouse to center. So I have no idea.

That's to say all of this would be completely unnecessary if devs would always implement both a hold and toggle option for games. I have found that most games use toggle which is annoying in that most of the time I prefer hold. Adding this could save a step every time I or someone starts a new game, or in games that don't have a hold option.

Platform information Win11Pro 21h2 OS Build 22000.1936. Wootility and Firmware version Wootility v4.5.5 Firmware v2.6.19

Keyboard Type Wooting 60HE ARM

[BigBrainAFK]

You will find that the lock state is kept internally in the OS not the keyboard. This applies to all lock keys (NumLock, ScrlLock, CapsLock)

[Doubs115]

You will find that the lock state is kept internally in the OS not the keyboard. This applies to all lock keys (NumLock, ScrlLock, CapsLock)

Although that may be true, are the on and off states different in the code? In other words it might not matter as long as the key sends the respective state to the system. Like and open loop circuit. Considering my second method of a workaround does indeed work but is just being janky, could this be fixed? The simplest solution witch I totally forgot was to fix DKS in that it shouldn't register a release in game. Is that the part I am missing when you say the keys state is on the OS side not the keyboard.