Wrong cursor orientation with Ubiquio 503g and Asus M530W

[drgoldie]

I've just tested our application (based on PocketHAL) on Ubiquio 503g and Asus M520W we just got and both return wrong cursor orientations. Using PHAL::GetKeyList() gives exactly the same results as directly using VK_LEFT, etc.

The effect is that pressing LEFT is reported as DOWN.
I haven't tested cursor on the 503g (the m530w has no touchscreen).
Except for that PocketHAL works fine.

Here are the logs of both devices:

ASUS M530w:

OEM String: "ASUS M530w"
PocketHAL (Version 1.0.4)
Display::Create( hwnd = 7C085330, W:0, H:0, O:0, S:1 )
Initializing display...
VideoDetect::DetectDrivers()
GDIDriver: Detect()
GDIDriver: Found W:240, H:320, D:16
VideoDetect: OS Version is 5.2
DriverVGA: Detect()
DriverVGA: Raw info: W:320, H:240, X:2, Y:640, FB:48F70AA0
DriverVGA: Native orientation is 0
DriverVGA: Found W:320, H:240, D:16
DriverVGA: Offset is 0
DriverVGA: Final framebuffer address = 48f70aa0
CreateDriver( 00000008 )
Initializing video driver...
DriverVGA: Initialize()
Driver initialized!
Success, returning display params to caller (W:320, H:240, O:0, S:2)

Ubiqio 503g:

OEM String: "TechFaith"
PocketHAL (Version 1.0.4)
Display::Create( hwnd = 7C085940, W:0, H:0, O:0, S:1 )
Initializing display...
VideoDetect::DetectDrivers()
GDIDriver: Detect()
GDIDriver: Found W:240, H:320, D:16
VideoDetect: OS Version is 5.2
DriverVGA: Detect()
DriverVGA: Raw info: W:320, H:240, X:2, Y:640, FB:495004A0
DriverVGA: Native orientation is 0
DriverVGA: Found W:320, H:240, D:16
DriverVGA: Offset is 0
DriverVGA: Final framebuffer address = 495004a0
CreateDriver( 00000008 )
Initializing video driver...
DriverVGA: Initialize()
Driver initialized!
Success, returning display params to caller (W:320, H:240, O:0, S:2)

[Kzinti]

GetKeyList() will always report "left" as VK_LEFT, up as "VK_UP", etc. no matter what you specify as an orientation.

PocketHAL will perform "device to logical" key translations in its WindowProc. Are you saying that this translation doesn't work properly on these 2 devices?

[drgoldie]

What I should have said is that my application is derived from the classes that come with the samples in PocketHAL.

So far my application worked on all devices. Yesterday I got these two new devices and it does not work correctly with those...

Daniel

[Kzinti]

Got it, I will investigate over the weekend.

[Kzinti]

Please try this version and let me know how it goes. Logging is enabled.

[drgoldie]

Great, this new version works fine on the Ubiquio 503g as well as the Asus M530W.

Are you using the OEM string to detect the device?
I am just asking because the OEM string on the Ubiqio 503g is not very unique.

I'll get an LG KS20 later this week. I've read that there were problems with PocketHAL on this device. Have these been already fixed?

Just a side note: PocketHAL also works fine on the new iPAQ 614c...

Daniel

[Kzinti]

Yes I am using the OEM String to detect devices. How common is the Ubiquio 503g?

As for the LG KS20, see this thread:

http://pocketmatrix.com/forums/viewtopic.php?t=28292

If you have access to a device, it would be great if you could test the DirectDraw enabled version of PocketHAL on it.

[drgoldie]

What I meant was that the 503g uses "TechFaith" as OEM string, which is the name of the OEM rather than the name of the device. I don't have any other devices from this manufacturer, but I guess they always use this string...

I'll get a KS20 later this week and will report on my findings.