Seeing (input) CAPS_LOCK DOWN+UP in the debug log

[mnsc]

I see some unexpected caps_lock outputs in the debug log when I hold down a default remapped caps_lock and scroll. Eg. to change zoom in the web browser. It seems to be perfectly symmetrical so that it does a caps lock down and up. So no issues with capslock staying on and this might be working as intended. Just wanted to point it out.

(input) CAPSLOCK DOWN [scan:0x3a virt:0x14]
(event) event_remapped_key_down
(input) <MOUSE INPUT> UP   [scan:0x00 virt:0xff]
(send) CTRL DOWN
(input) CAPSLOCK DOWN [scan:0x3a virt:0x14]
(input) CAPSLOCK UP   [scan:0x3a virt:0x14]
(event) event_remapped_key_up
(send) CTRL UP

[ililim]

To clarify in the logs you've shared here I don't see any capslock outputs: capslock is only listed for inputs.

The logs could probably be clearer, but an "(input)" means that you pressed the key keyboard, and "(send)" means that DKR has sent a virtual output.

As for the random capslock inputs, that's interesting. Perhaps Windows sends new key events when scrolling while holding down a key?