Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!rochester!udel!burdvax!sdcrdcf!trwrb!cadovax!keithd
From: keithd@cadovax.UUCP (Keith Doyle)
Newsgroups: comp.sys.amiga
Subject: Re: MaxXMouse/MaxYMouse, was Intuition don't touch
Message-ID: <1850@cadovax.UUCP>
Date: Fri, 6-Nov-87 18:01:56 EST
Article-I.D.: cadovax.1850
Posted: Fri Nov  6 18:01:56 1987
Date-Received: Mon, 9-Nov-87 04:52:01 EST
References: <8710312052.AA12848@cory.Berkeley.EDU>
Reply-To: keithd@cadovax.UUCP (Keith Doyle)
Organization: Contel Business Systems, Torrance, CA
Lines: 24

In article <8710312052.AA12848@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>	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.

DPaint and IFF ANIM files exist that may be larger than the current 
workbench.  Any program that displays these, and provides mouse
interaction (as mine does) gets caught by the "bug".  Distribution
of PD demos that you can just "put the disk in df1: and click on
the icon" becomes impossible without some kind of workaround.

Imagine a slideshow program that doesn't know how big the screens are going 
to be, can be run in df1: from anybodies CLI or WorkBench boot disk, and 
provides mouse interaction while the images are being displayed.  
Imagine the slideshow supports IFF overscan and IFF ANIM.  Morerows does not 
address the problem.

BTW, you won't have to just imagine for long.  Expect a "now shipping"
product announcement around Thanksgiving.

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