Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!lll-winken!ames!uakari.primate.wisc.edu!aplcen!uunet!mcsun!hp4nl!kunivv1!root
From: dueker@xenon.arc.nasa.gov (Chris Dueker)
Newsgroups: comp.sys.amiga
Subject: Re: uncensored wild copper?
Summary: PAL vs. NTSC
Message-ID: <42929@ames.arc.nasa.gov>
Date: 15 Feb 90 18:45:01 GMT
References: <11019@baldrick.udel.EDU>
Sender: usenet@ames.arc.nasa.gov
Reply-To: dueker@xenon.arc.nasa.gov
Organization: NASA-Ames Research Center
Lines: 24

In article <1047@kunivv1.sci.kun.nl>, root@kunivv1.sci.kun.nl writes...
> 
>It would be an even better idea to have all programmers test for the
>screen size if they open a screen or a window. There are just *too many*
>programs (from the American side of the Atlantic) that plainly ignore
>the fact that my Workbench screen is 672 * 266 pixels, and insist on
>opening screens of 640 * 200, or that limit their window sizes to that.
> 
>ovb11@cs.kun.nl (Olaf 'Rhialto' Seibert)
>Freely_Distributable=Greetings(Not_For_Any_Commercial_Purpose)->
>        Olaf.Seibert;
> 

I'm all for that!  However, other than allowing a window size to go up
to 672 x 266, what else is needed (or useful) for both types?  How does
one test for PAL vs NTSC environment?  Anything else?

------------------------------------------------------------------------
"Ah, Benson, you are so mercifully free of the ravages of intellegence!"
"Oh, thank you, Master!"             - from the movie, TIME BANDITS
------------------------------------------------------------------------
dueker@xenon.arc.nasa.gov        |   Chris Dueker (The Code Slinger)
dueker@krypton.arc.nasa.gov      |   Computer Sciences Corp.
duke@well.sf.ca.us               |   Mtn. View, CA