Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: comp.sys.amiga
Subject: Re: MaxXMouse/MaxYMouse, was Intuition don't touch
Message-ID: <8710312052.AA12848@cory.Berkeley.EDU>
Date: Sat, 31-Oct-87 15:52:57 EST
Article-I.D.: cory.8710312052.AA12848
Posted: Sat Oct 31 15:52:57 1987
Date-Received: Thu, 5-Nov-87 04:01:17 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27

>A note to morerows users. We are using a much more elegant way to control
>wb size then the morerows hack, so we do not plan on supporting the
>morerows magic.

	No problem... morerows is the type of program you run once then
forget about.  If the new release will have overscan support in preferences,
then there is no longer any need for the morerows hack, and application 
programs won't know the difference.

	Speaking of which, there is also a philisophical angle to all of this.
There are many people out there who's monitors cannot support an overscan
screen.  I think it would be incredibly stupid for developers of software to
'force' an overscan screen on such people.

	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.

	This whole MaxXMouse/MaxYMouse problem is due to openning screens
which are larger than the workbench.  My answer to all your complaints are,
simply, USE MOREROWS AND DON'T WRITE APPLICATIONS WHICH OPEN SCREENS 
PHYSICALLY LARGER THAN THE WORKBENCH'S.  As far as I'm concerned, the bug
doesn't exist.

					-Matt