New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fn+Numpad Enter issue #963
Labels
question
Further information is requested
Comments
@DarkEdgeXD do I understand correctly that you have M-keys row as well? |
@seerge Yes, the layout is as the image shows: The M4 key emits WMI event 56 while the Fn+Numpad Enter emits WMI event 181 |
@DarkEdgeXD try this build |
@seerge Works perfectly! :) Thanks a lot! |
Great, closing as completed then |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Fn+Numpad Enter follows the behaviour of the M4 key without an option to change the behaviour since v0.102 prerelease.
Clear scenario to Reproduce
Pressing Fn+Numpad Enter and then the M4 key
Expected behavior
A seperate Fn+Numpad Enter binding in extra
App Logs
log.txt
Desktop (please complete the following information):
Screenshot
Asus software
Tried with both no ASUS Services running and only ASUS optimisation running.
The text was updated successfully, but these errors were encountered: