feat: windows-interception-keyboard-hwids

[jtroo]

Describe your changes. Use imperative present tense.

Add capability in Windows+Interception to specify keyboards to intercept and passthrough others.

Checklist

• Add documentation to docs/config.adoc
  • Yes or N/A
• Add example and basic docs to cfg_samples/kanata.kbd
  • Yes or N/A
• Update error messages
  • Yes or N/A
• Added tests, or did manual testing
  • Yes

[CosmoDm]

I just compiled the code from the interceptonedev branch to try out the new windows-interception-keyboard-hwids functionality.
Unfortunately, kanata gives the same (null) hwid for all connected keyboards.
PS: hwid for mouse is ok.

[jtroo]

@CosmoDm

Are the keyboards plugged into a usb hub - which is then plugged into your computer? I've noticed that interception (and maybe Windows?) can't differentiate devices on the hub.

[CosmoDm]

@jtroo
No, not through the hub.

The keyboards are connected in different ways: one directly to the USB port with a cable, second one via 2.4GHz and the third via Bluetooth.

[jtroo]

@CosmoDm I think I found the issue, which is that the buffer was too small. I increased the buffer size, could you try again?

[CosmoDm]

@jtroo

With the increased buffer (512), the keyboards identified as device #4 and #8 were successfully detected. But device #6 did not.
I increased the HWID_ARR_SZ to 1024 and the hwid for device #6 was also detected.
I was wondering how much of a burden this increased buffer gives and tried to find the best option. In my case, HWID_ARR_SZ == 768 works for all three keyboards.

Nice project, by the way. Thank you!