Skip to main content

Rescaling contents screen size

4 replies [Last post]
jhchang
Offline
Joined: 2009-11-30
Points: 0

Hi all.
I successfully ported phoneme feature(got SVN latest version and patched davy's codes) on WVGA windows mobile target, but our contents only supports QVGA, so it displayed on the left top conner of target screen.

I wanna display contents using full target screen.
Is threre anyone who already solved this issue?

please give me some guides or code snippets.

In case I have to rescale screen image and touch coordinates,
is there any performance issue. if then how to solve it?

Thanks in advance!~

jaehoon.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
davyp
Offline
Joined: 2007-01-03
Points: 0

Can you check if my builds for Windows Mobile 2003 achieve what you are trying to do?
They do a 96dpi emulation on 192dpi devices so that your midlet is automatically rescaled
from QVGA to VGA and WVGA resolutions.

Davy

jhchang
Offline
Joined: 2009-11-30
Points: 0

Hi davyp.

I tested with your phoneME Feature - MIDP rev20166 for Windows Mobile 6, It automatically rescaled contents screen size(320*240) fit to Target screen size(800*480) exactly as you described.

but my build didn't.

I built it with version got from the SVN and updated all your patch.
Did I miss something or shoud I have to get another version?

Thanks.

Jaehoon.

Message was edited by: jhchang

davyp
Offline
Joined: 2007-01-03
Points: 0

The trick is to fool Windows Mobile 6 that you are running an application built for an
older OS that does not support 192dpi resolutions.

Check the following cldc and midp build configuration files and change the windows ce
version from 0x501 to 400 and any occurrence of windowsce,5.01 to windowsce,4.00

cldc/build/share/jvm.make
midp/build/common/makefiles/evc.gmk

That should do the trick.

Davy

jhchang
Offline
Joined: 2009-11-30
Points: 0

Hi davyp,

It works well.

I really appreciate your kind and prompt answer.

Thanks,
Jaehoon.