GAPI and virtual key code for 4th button

[werner]

Hi all,

I have a Jornada 568 that has the standard 4 buttons on the bottom of the device plus the arrow keypad. The GAPI routine GXGetDefaultKeys only returns data for vkA, vkB and vkC. Is there a standard hardware code for "vkD" or that fourth button? On my device its virtual key is 213. The others are 209, 210 and 211 and vkStart is 212.

Are these fairly standard? What are people doing to query that 4th button? I'm using GetAsyncKeyState but don't want to hardcode in 213 if it's incorrect.

Thanks for any info.

Werner Sharp
http://www.sharp-software.com

[BurningSheep]

These codes differ from device to device, I would consider letting the player assign the keys to his preferred configurations. Also there should be a list of these keycodes around here somewhere on the forum.

[Dan East]

I was about to start a new thread on this, until I found this thread. Anyway here's my post:

GXGetDefaultKeys only returns the values of 3 of the 4 hardware buttons on the front of a PPC (that's all the GXKeyList struct allows).

How are others determining the value of that 4th key? On the a716 it happens to be GXKeyList::vkC-1, however that doesn't hold up with the a620.

Thanks.

Dan East

[Kzinti]

[Dan East]

This is for my PSX Adapter, which does not / need not actually access the display. I'll have to take a closer look at PocketHAL.

How does PocketHAL manage this? Are these values hard-coded by device type? Or is it able to obtain the additional information from the lower level drivers that it accesses directly?

Dan East

[madfrog]

[Dan East]

[mlepage]

I think getting key values like this should be in a small dedicated library of its own. Such a library would work with GAPI, GapiDraw, PocketHAL/Frog, etc.

[Kzinti]

[Dan East]

[mlepage]

[Kzinti]