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

bindkey(number) do not respond on raspbian #591

Closed
jakpanu opened this issue Sep 11, 2019 · 5 comments
Closed

bindkey(number) do not respond on raspbian #591

jakpanu opened this issue Sep 11, 2019 · 5 comments
Labels
bug platform multi-platform issue

Comments

@jakpanu
Copy link

jakpanu commented Sep 11, 2019

I try to use bindKey to do something when I press "1" or other numbers on a keypad. Below code is run normally on Windows. But on Raspbian, its response only when I press "c" but no response when I press "1" on the keypad. What's wrong?

from appJar import gui

def pnt(a):
print(a)

with gui("xx") as app:
app.bindKey("c", pnt)
app.bindKey("Key-1", pnt)

@jarvisteach
Copy link
Owner

It's working fine on Mac as well. I'll need to do some testing on a Pi...

jarvisteach added a commit that referenced this issue Sep 28, 2019
@jarvisteach jarvisteach added the platform multi-platform issue label Sep 28, 2019
@jarvisteach
Copy link
Owner

jarvisteach commented Oct 12, 2019

I've tested this on my pi - and I get the expected response when I press the 1 key.

@jakpanu - does it work when you're pressing 1s along the top row?

Or, maybe it is a numlock issue?

@jarvisteach
Copy link
Owner

OK, just tested this direct on the pi (not through VNC) and it's definitely a keypad issue.

It must be that there's a different binding for the keypad, I'll need to get digging

@jarvisteach
Copy link
Owner

The bindings for keys on the keypad are: KP_ for other keys it's Key-

So for now, if you are adding a number key, I will bind both the keypad and key to the same event

jarvisteach added a commit that referenced this issue Oct 12, 2019
@jarvisteach
Copy link
Owner

Hopefully this resolves it

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

No branches or pull requests

2 participants