Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!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: <34008@sun.uucp>
Date: Mon, 16-Nov-87 16:51:48 EST
Article-I.D.: sun.34008
Posted: Mon Nov 16 16:51:48 1987
Date-Received: Thu, 19-Nov-87 00:19:40 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

[Has anyone *not* commented on this subject?]

In article <2272@gryphon.CTS.COM> jdow@gryphon.CTS.COM (Joanne Dow) writes:
>Sorry, Chuck, I have to disagree with you strongly regarding what "morerows"
>"tells" a program.

The point I tried to make was that you can open a screen of size [NDC,NDR]
because that is what size the workbench is. Opening a screen larger than
this *may* be a useless gesture if there is someone like myself who has made
their workbench extend right to all four edges of the screen. 

Enhancement Request for Dale : If you open a screen that is smaller than 
the maximum size that NormalDisplay variables indicate it could be, would 
it be possible to build the copper list such that the smaller screen opens 
'centered' in this larger area?

>Further your friend who returned VideoScape is within his rights I suppose. He
>is also sadly misinformed regarding what the authors of VideoScape intended.
>I'll ask him (indirectly) whether he'd like his normal TV pictures to have a
>black boarder around them of wasted pixels or not? VideoScape is designed to
>produce a TV-like picture. Hence it uses maximum overscan. True this cuts
>off some of the picture. But it really looks a lot nicer than having any silly
>frame around the picture.

What he was complaining about were some canned demos that put interesting
things into the overscan area (like titles) and looked really poorly framed
on his TV.

Joanne's and Keith's comments earlier were certainly valid w.r.t. eliminating
the border, and overscan viewports can do this nicely. If you put things that
need to be reached interactively with the mouse in the 'overscan' area you 
will have problems on cheap monitors because now your mouse pointer may
disappear off the edge of the world. So to summarize my opinion on these 
matters, use overscan all you want to eliminate borders, please restrict
where you put things the mouse needs to get to within the [0,0 ... NDC,NDR]
boundaries. 

--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.