Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!udel!burdvax!sdcrdcf!trwrb!cadovax!keithd
From: keithd@cadovax.UUCP (Keith Doyle)
Newsgroups: comp.sys.amiga
Subject: Re: invisible windows.
Message-ID: <1793@cadovax.UUCP>
Date: Tue, 13-Oct-87 14:17:13 EDT
Article-I.D.: cadovax.1793
Posted: Tue Oct 13 14:17:13 1987
Date-Received: Thu, 15-Oct-87 06:44:29 EDT
References: <8710060554.AA05630@cory.Berkeley.EDU>
Reply-To: keithd@cadovax.UUCP (Keith Doyle)
Organization: Contel Business Systems, Torrance, CA
Lines: 41

In article <8710060554.AA05630@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>>Hey gang, I was wondering what the Commodore approved method for changing
>>IntuitionBase->MaxXMouse and IntuitionBase->MaxYMouse is, so your pointer
>>can move wherever needed on an overscan screen.  Without modifying them,
>>the mouse will only move within a 320x200 rectangle within a 352x220
>>screen.

>	What version of the OS are you using?  My mouse has no problems with
>an overscan screen.

Well, try this, and see if you still say that:

1) start from a STANDARD 640x200 workbench screen.

2) invoke a 'C' program that does a:
	a) OpenScreen of an overscan screen
	b) waits so you can try stuff

3) Try moving the mouse on this overscan screen.  You will notice the
   mouse still thinks it's got a standard 640x200 screen space and will
   not move all the way to the lower right corner.

This happens on V1.2.  According to Carolyn at CBM, this has been a problem
because the MaxXMouse etc. values are in 'don't mess with it' space in
IntuitionBase.  Carolyn indicated they may be coerced into not moving this
stuff because there is presently no alternative but to modify these values
and we need the functionality.

Using MoreRows on a WB does not exhibit this problem, because it gets
around it by configuring Preferences so that the system will automatically
start up with the correct parameters in MaxXMouse etc.  Only if you start
with a smaller screen and do an OpenScreen of an overscan screen do you
get in trouble.

BTW, Here's one vote for CBM not moving these values, as it will definately
break our soon-to-be-released program.  (or rather, our program will
probably break something else, by modifying stuff that isn't there
anymore).

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