PocketMatrix

Ok, not sure if it is something Im doing but Im getting a few reported errors with GD3.6a..


1. Im having a few people report lockups on x50v's with WM5 until they update to the newest firmware update, but those same people didnt have problems with 3.01...

2. Cingular Blackjack(SGH-i607) owners are reporting turned screens so dont come up right in NORMAL orientation.

3. A HP6915 square screen owner is now reporting that it is drawing too big on his device and this was working correctly in 3.01...

Again, Im not sure if 1 and 3 might be something Im doing, but they both worked on the 3.01 based code, but are now being reported broken on my upgrade to 3.6..

Anybody else seeing similar ??

Thanks

Is there any code that you suspect might be causing the problem. If so if you could share a snippet it might help.

Currently I have no users so no real life feedback. However I am running on Dell x51v without a problem. This has worked on v6 of the firmware and still ok on latest v12 firmware.

Hello,

Easiest I guess would be to send them the GapiDraw sample programs and ask them if they work correctly (for example rotating the display in the collision sample etc). If they work the issue is most probably with your code.

Regarding button mapping, I would recommend to add an option to your game to allow the user to map any key to a function.

Sincerely
Johan

Thanks for the reply.

I would assume that for the Blackjack it is not my code, as it should look exactly the same as the Motorola Q, but is not working correctly on the BJ and is on the Q... and I am not doing anything specific to the Q only... Has it been tested on one?
(Pretty much the same as the sample applications).

And since this is a Smartphone I am going under the assumption that A is the left softkey and B is the right, like on all other devices, but this does not seem to be the case(and I would think needs to be).

Thanks...

Hi,
I'm currently testing on a Samsung I320, and I have a similar key problem,
the left and right soft menu keys are triggered by the keys 7 and 8
This is with GD3.5 since I have a link problem with GD3.6

Vincent.

Your screen orientation seems to work correctly??

Ok, Johan....

To support the Blackjack(Oem String: 'SGH-i607') and Im guessing exactly the same for the SGH-i320 as well, you need to probably do the same thing as the Q.


keylist.vkA = 112;
keylist.vkB = 113;
keylist.vkC = ?; (what is 'C' set to on the Q?)

and a starting rotation of GDDISPMODE_ROTATE90CW

and then Im having to rotate the action keys too...

---------------------------

I havent got reports from Dash Users(HTC Excalibur), but if this device isnt supported I can probably get a hold of people and find out the same type of info, as these LS smartphone devices are selling pretty good, and only getting more popular!

Still not sure what happened to the HP69XX square PPCs??

I loaded up the Minimal app, set

config.dwDisplayMode = GDDISPMODE_ROTATE90CW

In the GapiDrawMain function but when running the app, it still displays it rotated 90 degrees CCW. In fact.. no matter WHAT value I put in there.. it still comes out rotated.

Running a Samsung BlackJack with WM 5.0, VS 2005 SP1 and GapiDraw 3.6a eval.

Yeah, I believe I have to do the rotation after the initial startup, which obviously can be expensive...

You mean like... per-frame!?

No just rotate after the initial load has been done,
which will cause a re-load of all the surfaces once.