>Palm mentioned that there would be larger screens in the future (thought
>Palm might not be the one who manufactures them...).
>
>This means you should not rely on the 160 constant but get it from
>WinGetDisplayExtent().
I guess if you are designing a game, or an image viewer, it would make sense
to check WinDisplayExtent(). But most regular (form based) apps have screen
size dependence hard coded in the form resources (i. e. regardless of the
screen size, all widgets are placed in the (0,0)-(160,160) rectangle).
I guess it would be possible to design size independent forms (e. g. by hand
coding something similar to Java's layout mechanism). But it would probably
be hard to get them to look good, because when the screen is as small as the
Palm's you pretty much want to know exactly where each element goes.
So for regular apps and the time being, I would say, just assume that the
screen will be 160x160. I think that is what "everyone else" does anyway.
// Niklas
