Jump to content


Photo

GAPI on the Motorola Q: what developers need to know

* * * * * 1 votes

  • Please log in to reply
23 replies to this topic

#21
jeiku

jeiku

    Newbie

  • Members
  • Pip
  • 8 posts
  • Devices:n/a
RE: The original post.

That would probably explain why I cannot get spvDuke3d to run on my Motorola Q. I'm really bummed about this.

  • 0

#22
zorba990

zorba990

    Newbie

  • Members
  • Pip
  • 9 posts

Yup, my bad code...thanks! I should add that its at least 3-4 times faster this way than will GDI.



I'm noticing that although direct screen writes seem to work fine on the
Treo 700p, I'm not getting a WM_ACTIVATE message when the phone
goes into its suspend state (the off button can invoke this or it can
invoke itself on a timer). So when the keylock dialog comes up,
Treo is automatically resuming my app, but I'm fighting the screen with that
dialog since my app was never suspended.

Is there a solution for this? The docs seems abit spotty about registering for
system power states where a suspended state is concerned.

  • 0

#23
zorba990

zorba990

    Newbie

  • Members
  • Pip
  • 9 posts



Edited by zorba990, 05 February 2008 - 10:34 PM.

  • 0

#24
wipeout2097

wipeout2097

    Newbie

  • Members
  • Pip
  • 2 posts
  • Devices:Moto Q 9h
Hi everyone, first post. :)

I'm sorry that I bumped this thread. I have the Moto Q 9h and the display is garbled when running myDoomCe4.exe. Emulators either get the same result or crash complaining about cbPitch = 352 or whatever that is.

I tried everything: flashing WM 6.1, using GAPI from www.wincesoft.de, I'm going to install Windows Mobile 6 SDK and try recompile the Doom executable and emulators for which there's source code available. But after 2 weeks I just can't stand this anymore and there's always something in my way that makes me drop the ball out of frustration

Please help me. Thanks again

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users