Toggle Key setup for Fn1 doesn't not transition to off state

[dchan0629]

Describe the bug Toggle Key configuration is setup for 'Fn1' Key. This intent is to use toggle key on 'Fn 1' to avoid the hold down of 'Fn 1' to use function layer 1. The observed behavior is that when 'Fn 1' is pressed, The toggle key function would function as if the 'Fn 1' key is held down. However, when the 'Fn 1' key is pressed again, the 'Fn 1' is not released to its off state. Therefore, the keyboard would be still on function layer 1 instead of switched back to the main layer. The workaround is to tab the 'Fn 2' key to have the keyboard switched to function layer 2 and released to main layer.

To Reproduce Steps to reproduce the behavior:

1. Setup Toogle Key for 'Fn 1'
2. Tab on 'Fn 1'
3. Type to confirm function layer 1 is active without holding the 'Fn 1' key
4. Tab on 'Fn 1'
5. Function layer 1 remains active instead of switched to main layer

Screenshots / Video N/A

Desktop (please complete the following information):

• OS: Windows 11

Wootility and Firmware version Wootiliaty v4.4.13

Keyboard Type Wooting 60HE ARM Firmware v2.6.3

[andreasterrius]

Can you describe a bit more for the workaround ? For me after transitioning to main layer after pressing Fn2 on my Fn3 Layer, it will require two press to toggle back to my Fn3 Layer.

[calt1]

Can confirm this bug. It's annoying as this would be such a useful function if it worked correctly.

Windows 10 Wootility v4.4.13 Wooting 60HE ARM Firmware v2.6.3

[dchan0629]

@andreasterrius The "workaround" I had described is to tap 'Fn 2' key to trigger the switch from 'Fn 1 Layer' to 'Main Layer via switch from 'Fn Layer 1' to 'Fn Layer 2' on key press and return to 'Main Layer' on key release. Obviously, the 'Fn 2' key should not be configured as toggle.