You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As you can see, it has no "normal" buttons or keys (indeed, I would suggest this is precisely the kind of peripheral for which input-mapper is ideally suited). However, the classifier in groups.py doesn't know what to make of this, classifies it as UNKNOWN and completely ignores it.
It would be nice to have a provision whereby I can say, "No no, this is a valid input device that generates valid events; please register it, anyway." This could be specified by USB vendor/product ID, the name registered with the kernel input system, or by whatever else is convenient for the program.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I'm working on a driver for the old Logitech G13 gaming keypad. Here's the current capability mapping (subject to minor change):
As you can see, it has no "normal" buttons or keys (indeed, I would suggest this is precisely the kind of peripheral for which input-mapper is ideally suited). However, the classifier in
groups.pydoesn't know what to make of this, classifies it asUNKNOWNand completely ignores it.It would be nice to have a provision whereby I can say, "No no, this is a valid input device that generates valid events; please register it, anyway." This could be specified by USB vendor/product ID, the name registered with the kernel input system, or by whatever else is convenient for the program.
Beta Was this translation helpful? Give feedback.
All reactions