Support for KC_INT and some extra keys (KC_KP_COMMA) for an ABNT2 layout about qmk_firmware

[mecanogrh]

If you want /? use KC_SLSH, how can you have #define BR_SCLN KC_SLSH outputting a semicolon? That doesn't make sense. If you define BR_SCLN to KC_SLSH, BR_SCLN will output a slash.

@mecanogrh when using the Brazilian ABNT2 keyboard layout (the one you choose in your OS as an input source), the scan code usually used for the slash outputs a semicolon instead, among several other things that are switched. It's the same thing with the german keyboard layout that switches the Y for the Z, and the french layout that switches Q and W for A and Z (among other things).

This repo itself has several mappings for alternate keyboard layouts, I'm just doing doing exactly the same thing but for the specific mappings of the Brazilian ABNT2 layout.

I hope it makes sense now. If it still doesn't may I suggest a little interesting experiment for you: change your OS keyboard layout temporarily to "Portuguese (Brazil ABNT2)" and type the slash key, see what gets written to your screen :)

You can ignore all the stuff about alternate layouts actually, the real issue is: how do I get the KC_INT1 and KC_KP_COMMA to be actually sent by the hardware? They seem to be ignored at the moment.

[mecanogrh]

Ok I understand now sorry, these input methods should be forbidden and all should be unicode coded in the input hardware :)
I tried KC_KP_COMMA on an US input method and it is indeed broken here as well (OSX), but I can't see any KP Comma in the input method so it looks quiet normal. One workaround if you need it straightaway is to give a shot to Ukelele if you are on OSX, it proved valuable for me to relocate special characters and dead keys (accents) before I got a planck.

[ezuk]

@Potz were you able to resolve this in the end? Or is this still a problem?

I have not solved this, no. It's been a while and I'm currently using a US-international variant but ideally I would like to get these keys working if I could only find a way. Unfortunately I lack the C skills to actually understand the firmware code.

[shelaf]

@Potz This problem seems to be similar to #312 .
If your problem is the same cause, would you like to try applying 6b8b332 patch or getting latest source code and rebuild your keymap.

YES!!! I can confirm that it works with the latest firmware!

Thank you very much, this is awesome! 😺 😸 😺 I'm gonna reactivate my little ABNT2 layout project now.

I updated my docker image to use the latest version of the firmware as well.