I'm not sure I get the point. Do you mean to solve the problem by making
all items relative to the screen resolution, or...?
And what happens when the differense is too big, for exp. Nokia 3650
with cca 178x208 px and some simens with 80x120 or so. What do you do
then? (Im just curious to know how is it done by others, no flame :) )
> I'm not sure I get the point. Do you mean to solve the problem by
> making
[quoted text clipped - 3 lines]
> with cca 178x208 px and some simens with 80x120 or so. What do you do
> then? (Im just curious to know how is it done by others, no flame :) )
Well, if the screen is that small, either dynamically downsize the
images when the MIDlet is loaded (downsizing by a factor of 2 is fast
and easy to do), or keep your images the same size and have a smaller
viewport. But I guess this greatly depends on the type of app you are
working with.
For instance, this works well for jump'n'run games or driving
simulators (with a 2D top-perspective). Then resizing might not even be
necessary, if it is ok to have a smaller viewport.
In my application I do just that. Image sizes are fixed, but the
amount of landscape you see depends on the size of your display. So if
your screen is small, you have to scroll more to get from A to B .. if
it is large, you scroll less.
regards

Signature
jb
(reply address in rot13, unscramble first)
Andrew Thompson - 19 Jul 2005 18:02 GMT
>> I'm not sure I get the point.
I was not sure I had one, I do no midlet development, but..
> Well, if the screen is that small, either ...
[snip Jakob's advice]
..yeah that. Couldn't have said it better myself. ;-)

Signature
Andrew Thompson
physci.org 1point1c.org javasaver.com lensescapes.com athompson.info
Beats A Hard Kick In The Face