Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!usc!pollux.usc.edu!papa
From: papa@pollux.usc.edu (Marco Papa)
Newsgroups: comp.sys.amiga.tech
Subject: Re: JRComm (Was Re: AMIGA too slow for speeds higher than 9600 Baud? HELP!)
Message-ID: <24468@usc.edu>
Date: 2 May 90 22:37:40 GMT
References: <892@tau.sm.luth.se> <6781@bula.se>
Sender: news@usc.edu
Distribution: comp
Organization: Felsina Software, Los Angeles, CA
Lines: 28

In article <6781@bula.se> Bjorn Knutsson <bjornk@bula.se> writes:
>In article <892@tau.sm.luth.se> d88-mbe@sm.luth.se (Michael Bergman) writes:
>>[Stuff deleted]
>>So come on guys: when you write a program, make the screen 255 high if it's
>>a PAL machine and leave the 200-line screens for the inferior NTCS mode.
>
>Just do what I do, keep bugging the authors until they fix it. (Right,
>Marco? :-) Not adapting to PAL screens where appropriate is a bug.

Right, right! OK, OK :-) [from a repented NTSC developer]

>Actually, I belive software should adapt to whatever resolution the
>user has selected as default for his system, regardless if this is a
>640*200 NTSC screen or something like the 704*568 I often use.

That is quite true, especially when you consider that we can now have
NTSC, PAL, morerows, A2024/Viking1, plus all the new ECS screen sizes.
I still see a lot of programs that "limit" the size of the window on
workbench to 640x400.  Not good.

Bjorn still hasn't convinced me that I should fill the bottom area with 
some more features (like in the A-Talk III phonebook) in the PAL version,
though :-)

-- Marco
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
"Xerox sues somebody for copying?" -- David Letterman
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=