Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!necntc!ames!amdahl!oliveb!sun!pepper!cmcmanis
From: cmcmanis%pepper@Sun.COM (Chuck McManis)
Newsgroups: comp.sys.amiga
Subject: Re: Intuition's "dont mess with these" fields...
Message-ID: <33210@sun.uucp>
Date: Fri, 6-Nov-87 12:50:14 EST
Article-I.D.: sun.33210
Posted: Fri Nov  6 12:50:14 1987
Date-Received: Sun, 8-Nov-87 20:44:00 EST
References: <1961@amiga.amiga.UUCP> <1825@cadovax.UUCP>
Sender: news@sun.uucp
Reply-To: cmcmanis@sun.UUCP (Chuck McManis)
Organization: Sun Microsystems, Mountain View
Lines: 40
Keywords: Intuition verboten nopokenzefields

In article <1845@cadovax.UUCP> keithd@cadovax.UUCP (Keith Doyle) writes:
>In article <2659@cbmvax.UUCP> andy@cbmvax.UUCP (Andy Finkel) writes:
>>You might try the morerows trick.  It may or may nor do what you
>>want...(yell at me later, Dale :-)  )
>
>Ok, what is the morerows trick?  I thought it just modifies the
>system-configuration, and then Intuition sets up the MaxXMouse/MaxYMouse.
>Unfortunately, I need to do it without requiring a reboot.

Keith, and others in this bind. Consider the following ...

One of the problems with 'overscan' is that not all monitors can handle
it. That means that if you put the screen into what you think is a 
reasonable overscan mode, the image may very well be off the edges of
the screen of some users. So how can you know ahead of time that what
the users screen can handle ? You CANT! However, when the *user* resizes
his screen intuition picks this up and you don't have to do anything 
different in your program, just open a screen to the smaller of 
your maximum desired screen/window size -or- the maximum intuition
screen/window size. The mouse will always travel to *all* parts of
this screen! When looking at it this way, the answer becomes obvious
(to me at least). 

For pre-1.2+ systems you supply morerows ( which last time I checked was
freely redistributable) and explain to the user how to set up the maximum
screen size that they are comfortable with on their monitor. Then your
application is 'well behaved' and doesn't open a window or screen bigger
than ( GfxBase->NormalDisplayColumns, GfxBase->NormalDisplayRows ). It's
supported, and will work in this and all future releases because you have
only used *public* variables in the GfxBase structure and when overscan
is officially blessed and supported Commodore will undoubtedly provide a 
means for the user to set up the maximum sized screen their display can
handle. 

As a suggestion to Commodore, why not provide a 'sizing' gadget on the
screen positioning box in preferences ? 

--Chuck McManis
uucp: {anywhere}!sun!cmcmanis   BIX: cmcmanis  ARPAnet: cmcmanis@sun.com
These opinions are my own and no one elses, but you knew that didn't you.