#13 Keycodes that are not on the list are left empty

keytouch-editor 3.1
closed-duplicate
nobody
None
5
2007-06-27
2007-06-14
Anonymous
No

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.

Ilya
iva2k@yahoo.com

Discussion

  • Logged In: NO

    It seems like keytouch's list of keycode names is much shorter than the one in linux kernel, see http://lxr.linux.no/source/include/linux/input.h

    So it won't support many defined keycodes.

     
  • Logged In: YES
    user_id=972280
    Originator: NO

    Ilya: "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."

    A keycode is not a name. It is just a label for the key so that it can be identified by programs.

    Ilya: "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."

    A keycode is not is scancode (the code that is sent by the keyboard). The user can even change the keycode and that is one of the thing that are done by keyTouch.

    This problem is related to the USB problem (see frontpage of http://keytouch.sf.net\) and is not a bug of keyTouch but a feature lack in the Linux kernel. So this is not a keyTouch-editor bug so I will close this bug report. Note that it will be fixed.

     
    • status: open --> open-duplicate
     
    • status: open-duplicate --> closed-duplicate