Skip to content
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

Keypad numbers don't work #20

Open
ashkitten opened this issue Oct 9, 2016 · 5 comments
Open

Keypad numbers don't work #20

ashkitten opened this issue Oct 9, 2016 · 5 comments

Comments

@ashkitten
Copy link

I tried to map keypad numbers (KP_0, KP_1, etc) and they do not work at all.

@anxest
Copy link

anxest commented May 7, 2018

Well, that does work for me, but thanks for giving me the name of the keys :)

@gonX
Copy link

gonX commented May 9, 2018

Make sure Num lock is on. Otherwise KP_1 will usually be KP_End.

@Ordoviz
Copy link

Ordoviz commented Aug 24, 2019

They only work if global-hotkeys is set to false. Don’t ask me why.

@zennyrpg28
Copy link

Got my numpad to work with global-hotkeys on by turning off num lock. I used the xev program in the console to tell me the name of the numpad keys. I used 1, 3, 4, and 6 which translated to End Next Left Right

@alkaris2
Copy link

alkaris2 commented Jan 3, 2021

Same issues I was having, Split Timer doesn't respond to the assigned Keypad keys when NumLock is ON, but will respond when NumLock is OFF. This should work with either state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants