I have a remote control & front panel button combo device. It has kernel driver that produces /dev/input/event<N> file ok. Some keys even work by default (volume up/down). Next, I create a new keyboard for that device in keytouch-editor, click "New" and press a key on device - keytouch-editor registers a key, but:
1. Scancode: "No scancode. This key is identified by its keycode."
2. Keycode: stays empty
3. When saving, a dialog shows up that says:
"The keyboard file has been saved successfully, but cannot yet be imported in keyTouch because it is not a valid keyboard file. The keyboard file contains an empty keycode."
4. Consequently, the file cannot be imported into keytouch with similar message.
Some keys work OK and show up with a name in Keycode.
It looks like keytouch-editor cannot deal with any keycode that it does not have a name for. Ironically, most keys that do have a name, already work without keytouch, but Manufacturers are coming up with new keys on their devices every day, and they don't work in keytouch. This makes keytouch & editor useless for a good deal of new devices.
Expected behavior: if keytouch-editor does not have a name for a keycode, it should use numeric keycode, hex preferred (for example, 0x123). It will allow use of ANY new key device with keytouch.
It would be also nice to show hex keycode next to its name for named keycodes, so designer/developer of new device has better understanding of which key is which.
Log in to post a comment.