Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ucla-cs!zen!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: Overscan and Blink
Message-ID: <8709222210.AA27263@cory.Berkeley.EDU>
Date: Tue, 22-Sep-87 18:10:29 EDT
Article-I.D.: cory.8709222210.AA27263
Posted: Tue Sep 22 18:10:29 1987
Date-Received: Fri, 25-Sep-87 01:31:51 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 12


	Overscan is a boon in many respects.  Since there is no standard
overscan resolution, programmers who want to take advantage of it usually
create software which conforms to a particular user's screen size.  This
also gives programmers more of an incentive to support PAL screens (or PAL
programmers to support US screens) which is inherent when you make the
GetScreenData() call.

	The only possible screwup occurs when a program does NOT check
the size of the workbench screen before openning an overscan screen.

				-Matt