Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!hplabs!sdcrdcf!trwrb!cadovax!keithd
From: keithd@cadovax.UUCP (Keith Doyle)
Newsgroups: comp.sys.amiga
Subject: Re: Intuition's "dont mess with these" fields...(solution?)
Message-ID: <1848@cadovax.UUCP>
Date: Fri, 6-Nov-87 14:22:29 EST
Article-I.D.: cadovax.1848
Posted: Fri Nov  6 14:22:29 1987
Date-Received: Sun, 8-Nov-87 22:48:41 EST
References: <1961@amiga.amiga.UUCP> <1825@cadovax.UUCP> <2631@cbmvax.UUCP> <1831@cadovax.UUCP> <4112@garfield.UUCP>
Reply-To: keithd@cadovax.UUCP (Keith Doyle)
Distribution: na
Organization: Contel Business Systems, Torrance, CA
Lines: 18
Keywords: Intuition verboten nopokenzefields

In article <4112@garfield.UUCP> john13@garfield.UUCP (John Russell) writes:
>--
>If, as was said before, the Intuition fields are automatically set correctly
>if the Workbench screen is in overscan, why not ship your program on an
>overscan Workbench disk of the correct screen size?

Except that only the end user knows what the "correct" screen size is,
and it may be different from invocation to invocation.  What my program
does, is set up the screen based on an IFF file it is given, which can vary 
from one invocation of the program to the next.  There is no "correct"
screen size in the case like this because it is 100% dynamic.  In fact,
it can even vary during a single invocation.  With my program you can
preload IFF files of varying sizes (resolutions) and switch between
them, thereby allowing a mix of overscan and non-overscan images if
desired.

Keith Doyle
#  {ucbvax,decvax}!trwrb!cadovax!keithd  Contel Business Systems 213-323-8170