Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!usc!rutgers!faatcrl!jprad
From: jprad@faatcrl.UUCP (Jack Radigan)
Newsgroups: comp.sys.amiga.tech
Subject: Re: JRComm (Was Re: AMIGA too slow for speeds higher than 9600 Baud? HELP!)
Message-ID: <1370@faatcrl.UUCP>
Date: 9 May 90 01:46:49 GMT
References: <1494@lpami.wimsey.bc.ca>
Organization: FAA Technical Center, Atlantic City NJ
Lines: 25

lphillips@lpami.wimsey.bc.ca (Larry Phillips) writes:

>Is the status line part of the normal screen as seen by the host? ie. does the
>host explicitly write out the status line itself in the same way that it writes
>out the rest of the lines? If not, I would not consider it part of the
>'screen'. You will, of course, have to have room for it there, but for
>communication purposes, it doesn't exist, so you only allow the host to muck
>with a 24 line screen. If it is treated as a normal line by the host, then
>ignore the above comments.

I've heard of a few systems that use the status line for their own use, but
they're certainly in the minority.  What I *was* trying to say that in both
cases you have a 25 line display, with the 25th line being optional, either
part of the display or the (as you pointed out) *local* status line.

More to the point with regards to cursor positioning, I *do* range checking
based on the legal (from JR-Comm's standpoint) size of the display.  What
I'm still fuzzy on is if I should allow a non-standard display (morerow'd or
PAL) go past the *normal* size since that allows the possibility of garbage
accumulating along the outter edges of the legal (from the remotes standpoint)
display size.

I hope I'm being a bit more clear on this.

  -jack-