🚀 go-pugleaf

In article 24579@enea.se, tope@enea.se (Tommy Petersson) writes:
>We have an application written in Visual Basic for use on normal
>VGA (640*480) monitors. More and more people have 800*600,
>1024*768 or bigger screens, so it would be fine to dynamically
>take that into account.
>

I find it quite difficult, in the "real world", to write an application such
that it is perfectly usable in any and all resolutions.  It's a nice goal, and
one can take steps in that direction, but it's tough to achieve, IMHO.

If you can restrict your application to a few resolutions, then you can make
life much easier on yourself.  640x480 VGA is pretty much the default, but
so many people use 800x600 SVGA its support is almost mandatory.  1024x768 is
not quite as popular, but as larger screen monitors decrease in price, the
number of users of this mode will increase.  The higher resolution modes are
still pretty much beyond the _average_ user, IMHO.  Anyone disagree here?

The answer then, is to try to come up with the most appropriate scaling factor
to support your chosen range of resolutions.  It's either that, or yield to
bunches of DATA statements with the coordinates/dimensions of your various
Windows widgets for each resolution.  I don't know how you could realistically
avoid a lot of trial and error testing, however.

I too would be interested in hearing comments/tips from other programmers who
attempt to make their applications resolution independent.

---

___________________________ John "HUTCH" Hutchinson _________________________
_________________ Fair Dinkum Technologies     Member - IAAD  _______________
________________ "No worries, mate... it's from Fair Dinkum!" _______________
____________ email: hutch@bellman.lanl.gov   GEnie: FAIR-DINKUM _____________