Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!usc!cs.utexas.edu!uunet!van-bc!rsoft!mindlink!a976
From: a976@mindlink.UUCP (Ron Tarrant)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Simple Overscan Display
Message-ID: <4210@mindlink.UUCP>
Date: 22 Dec 90 02:05:21 GMT
Organization: MIND LINK! - British Columbia, Canada
Lines: 24

> BAXTER_A@wehi.dn.mu.oz writes:
> 
> This CAN NOT be derived from ANY system information. Under WB2.0 you can find
> out the "text" and "overscan" sizes of the screen as selected by the user-
> which are supposed to represent what you want to know, and these are used to
> set the workbench size. But that in no way stops the user choosing to have
> a one inch black boarder all round the active screen, which you won't know
> about.
> 
> An alternative is just to open an overscanned screen (just use
> overdimensional
> values when specifying screen size) and expect the user to reset the monitor,
> but most people on finding the screen cut off by the bezel will assume
> you are a shit programmer and not use your program.
> 
> Regards Alan


If I were writing a word processor or a spreadsheet I would expect people to
think things like that. However, I'm writing a video tool. If a video tool
DOESN'T do overscan then your comment about s*** programmers would apply... in
spades!
-Ron Tarrant
a976@Mindlink.UUCP