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

Key code to key name are not necessary one to one mapping #6

Open
ek9852 opened this issue Dec 20, 2017 · 1 comment
Open

Key code to key name are not necessary one to one mapping #6

ek9852 opened this issue Dec 20, 2017 · 1 comment

Comments

@ek9852
Copy link

ek9852 commented Dec 20, 2017

Currently the code assume key code and key name are one-to-one mapping.
Actually it is not, e.g. BTN_MISC and BTN_0 have same key code.
This will result in some key name not working property in conf file.

@gandro
Copy link
Owner

gandro commented Dec 20, 2017

Thanks for the report! :)
Unfortunately, this is unlikely to be changed, as I do not maintain this project anymore.

If anybody would like to take ownership of this project and maintain it, please let me know - I'm happy to transfer the GitHub repository to someone else (and potentially change the license to MIT or something more appropriate).

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

2 participants