🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.mail.elm
Article #3633

Re: List of enhancements

#3633
From: Scott Ophof
Date: Thu, 07 Jan 1993 11:53
29 lines
1741 bytes
On Wed, 30 Dec 92 12:45:47 GMT tanner@cdis-1.compu.com said:
>) Isn't there any way for a program to detect that it has been
>) requested to already display the next screen before it has
>) ended updating the current screen?
>Of course it is possible.   The  5.1  version  of  my  employer's
>application  package  does  this  very  thing.   Not only are the
>screen updates blindlingly fast,  but  they  are  skipped  if  it
>appears  prudent  to  do  so  because  another  screen  has  been
>requested.

"Blindingly fast" relates of course to a dataline speed which is
many times higher than 2400bps, right?
An opsys I like very much is also *fast* (at 56Kbps, who wouldn't
be!), but it also does partial screen updates by comparing the data
the old with the new data, redrawing only the differences.  Still,
they were smart enough to include a "fullscreen refresh" for "dirty"
datalines.  Not on a per-application level, but at opsys level.

Now, how is this accomplished?  Hopefully not covered by some
patent?


>I assure you that it makes testing easier when you don't have  to
>wait for useless screen plots.  Yes, I think that users prefer it
>this way also.

Glad to hear that at least somebody shares my view re this.  :-)
Does anyone have other opinions/ideas/suggestions?
Technical Details
Message-ID: <9301071151.AA27377@SERVER.uwindsor.ca>
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!not-for-mail
References: <1TA04GO@cdis-1.compu.com>

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!cs.utexas.edu!not-for-mail
From: ophof@SERVER.uwindsor.ca (Scott Ophof)
Newsgroups: comp.mail.elm
Subject: Re: List of enhancements
Date: 7 Jan 1993 05:53:34 -0600
Organization: UTexas Mail-to-News Gateway
Lines: 31
Sender: daemon@cs.utexas.edu
Message-ID: <9301071151.AA27377@SERVER.uwindsor.ca>
References: <1TA04GO@cdis-1.compu.com>
NNTP-Posting-Host: cs.utexas.edu