That is really neat. So correct me if i am wrong. You wrote the driver to interface with the keyboard and then created the keycode.tbl file. Does the keycode.tbl file work similar to the keyhelper.xml file. So if you can make a custom keycode.tbl file you dont need keyhelper???
Yes that's right. You can do all kinds of key remapping with keycode.tbl because it's the master keytable for Qtopia. You can even do things like add new scan codes and unicode characters, which keyhelper can't do.
Keyhelper has a few advantages of it's own. When you edit keycode.tbl you have to restart Qtopia, whereas keyhelper can make changes on the fly. Also, keyhelper has other features besides remapping that can be useful, like app-launching.
How do you get the keycode for each key. Is there a comand for it.
I know on a *nix box you can grab the key scan codes and make a new map from that. Is this similar??
I mostly got the scan codes and QT key codes from reading the existing keycode.tbl. In a few cases, I just created my own new scan codes which the driver sends and added them as extra lines to keycode.tbl. The "path" from keystroke to screen goes like this:
1) user presses key
2) keyboard generates key code and sends to driver (these codes are specific to this keyboard)
3) driver translates key code from keyboard to scan code, and injects the key event into Linux Kernel
4a) if you are in console mode the kernel translates scan code to ASCII as defined in tosa_keyboard.c in the Sharp kernel.
4b) in, QTopia the scan code is translated to the QT key using keycode.tbl
5b) if you are running keyhelper, that's yet another translation layer.
4c) in X11, the X server will translate scan codes into X key events using the X keymap.
If I start playing around with pdaXrom, I'll try to create a good X keymap for this keyboard. If I have to, I may write a seperate XInput driver, so that it can take special advantage of X11 features.
Sorry for all the quesitons. I am attempting to learn and be able to use all the power of the Zaurus. It is a very powerful tool when you understand how use all its capabilites. I guess that is why Sharp called it a "personal moble tool" and not a just a PDA.
No need to apologize. I'm enjoying improving my 6000 experience right now, and I hope others will jump in too. I agree that the community has been too small and fragmented, and I'm hoping we can pick up where Sharp left off and realize the awesome potential of this model. It already seems way more advanced to me than a year ago because of the great work people have done.
