Closed inhaledesign closed 2 years ago
Yeah this happens because we don't actually send "numlock" keypress when the user activates the numpad (we only set the brightness). This is on my todo list (integration with system numlock).
For now, a quick solution would be to find a setting in your DE that specifies the numlock behaviour on startup. For example, KDE allows forcing the numlock to be set to "On" at startup. After that, this driver will work properly.
Or an even simpler solution, use xdotool
(or some equivalent for wayland) to send a "numlock" keypress.
@inhaledesign Give it a try now- should be fixed in the latest version (v0.3.0)
This has been fixed. Closing due to inactivity.
I confirm that the problem is fixed in the latest version, thanks !
Expected behavior: Touching numbers 1-9 on touch pad will trigger a keypress of t heir respective number. Actual behavior: Touching numbers 1-9 on touch pad trigger secondary functions (9 will page up, 3 will page down, etc.) Hardware: Asus Zenbook UM425Q
Steps:
Comments: Other buttons, such as backspace, '=', and the dimmer button, work as expected. I'm assuming that it's behaving as if numlock is off. Unless I'm blind, there doesn't appear to be a numlock key on the keyboard, so I can't turn it on.