gdkeylist and the Axim x50v

[dan.p]

[Johan]

[dan.p]

[fzammetti]

[dan.p]

[dan.p]

I think you guys confused me. I was under the impression that the same keys could have different keycodes on different devices (not email, etc., but in terms of key position - ie; the key all the way to the left).

But that's okay, it made me dig around the documentation. I found this:

http://msdn.microsoft.com/library/defau ... agemap.asp

I may not be able to look at the buttons in terms of email, contacts, etc., but I can look at the buttons on any device in this manner:

K1 K2 D-Pad K3 K4

Given the documentation:

K1 = 193
K2 = 194
K3 = 195
K4 = 196

The keys on any device read from left to right. I would expect GDKEYLIST vkA, vkB, etc. to coincide in the same manner:

K1 = vkA = 193
K2 = vkB = 194
K3 = vkC = 195
K4 = vkD = 196

Unfortunately it doesn't at all. Not only that, but there's no vkD for the fourth keycode. There's vkStart, but that's mapped to the button in the middle of the D-Pad.

Once you look at keys generically, you can get away without having to program an "options" screen. Arvale has done this. If you download the demo, and start playing the game, you'll notice that the keys coincide with the toolbar menu items. I = Item, K = Key:

I1 I2 I3 I4
K1 K2 K3 K4

This is exactly what I was looking for. If I am still incorrect, please correct me.

[Mapman]

Well just to confuse things even further, be aware, on my Fujitsu Siemens Pocket LOOX 610 if you press and release the buttons quickly I receive the following double key codes:



K1 = 213 - 193
K2 = 210 - 194
K3 = 212 - 195
K4 = 209 - 196

However, when pressing and holding the buttons I get the following:



K1 = 213 - 193
K2 = 210 - 198
K3 = 212 - 195
K4 = 209 - 200

Note the changes in K2 and K4.

[dan.p]

I assume the keydown would have the regular keycodes, but the keyup changes depending on how long you hold them?

[InexorableTash]

FYI, the reason GapiDraw only exposes A, B, C is that the PocketPC-specific API it derives from - GAPI (Game API) provides device-independent lookup values for (you guessed it!) only 3 buttons - A, B and C.

Basically, PocketPC OEMs are able to ship a GAPI implementation with their devices and it's up to the OEM to decide what A, B and C should be for their device. Although nearly all PPCs today have the (1, 2, D-Pad, 3, 4) arrangement, my first PocketPC only had the D-Pad plus three buttons on the front of the device. Without dictating to the OEMs what hardware they had to ship, GAPI therefore must be a lowest-common-denominator sort of thing.

(What'd be nifty is some sort of abstraction that used a table in an external file which had all the known devices and key mappings, and this file could be updated. Failing that, an options screen seems like a good idea.)