[Bug] Can't map Numpad Enter when Consume Mapped Inputs is enabled

[i-report-bugs]

When I map Numpad Enter to a different keyboard key, for example, the Space Bar, and I turn on "Consume Mapped Inputs" for the device, it doesn't work outside of PadForge. The preview works properly but on other places, it reverts to the default behavior (Numpad Enter). When I turn off "Consume Mapped Inputs", it works again but obviously now I get dual inputs.

I haven't tried the option of hiding the entire device because I still want to use other keys normally.

Here's a video demonstrating it in action. I mapped Numpad 3 to Backspace and Numpad Enter to Space. As soon as I consume the input, only Numpad 3 continues working as expected. Numpad Enter is not mapped.

padforge.numpad.enter.bug.mp4

[hifihedgehog]

You found a real bug, and it's fixed on the development branch. It ships with the next release.

Numpad Enter and the main Enter key send Windows the same key code. Only an "extended key" flag marks the one on the number pad. PadForge's key reader uses that flag to keep the two apart, which is why your mapping worked in the preview. Consume Mapped Inputs, the part that blocks the original key from reaching other programs, looked the key up without that flag. It never found Numpad Enter in its list and let it through, so other programs got Enter as well as your Space. Numpad 3 has a code of its own, which is why it worked.

The same mistake ran the other way too. Consuming the main Enter key also blocked Numpad Enter and treated it as Enter. That's fixed as well, so the two keys now behave as separate keys whichever one you map.

With the fix, your setup works as you expected: Numpad Enter sends only Space, and Numpad 3 sends only Backspace. Every other key on the keyboard keeps typing normally. You don't need to hide the keyboard.

Tests cover the fix, but no one has run the fixed build with a real keyboard yet.

[i-report-bugs]

Awesome, thanks! ❤️