Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!tektronix!tekcrl!tekfdi!bobb
From: bobb@tekfdi.TEK.COM (Robert Bales)
Newsgroups: comp.sys.amiga
Subject: Re: MaxXMouse/MaxYMouse, was Intuition don't touch
Message-ID: <1432@tekfdi.TEK.COM>
Date: Tue, 3-Nov-87 00:19:48 EST
Article-I.D.: tekfdi.1432
Posted: Tue Nov  3 00:19:48 1987
Date-Received: Fri, 6-Nov-87 04:03:58 EST
References: <8710312052.AA12848@cory.Berkeley.EDU>
Reply-To: bobb@tekfdi.UUCP (Robert Bales)
Organization: Tektronix, Inc., Beaverton, OR.
Lines: 21

In article <8710312052.AA12848@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU
(Matt Dillon) writes:

>	So what you do is (A) write your program such that it can handle any
>screen size... an extremely easy thing to do, and (B) never open a screen
>physically larger than the workbench.  Thus anybody who uses an overscan 
>workbench (morerows) would automatically inform applications that it is O.K.
>to use overscan themselves.

I think "never" is too strong a word. Consider any type of video application.
For the "control" part of the program, I'll want to see everything on screen
--> normal scan. But for the "display" part, I want overscan to eliminate
borders on the videotaped image.

This may not be important in the context of this discussion, as I am unlikely
to use the mouse during thr display portion of the program.

   Bob Bales
   Tektronix, Inc.

I help Tektronix make their instruments. They don't help me make my opinions.