Path: utzoo!attcan!uunet!ncrlnk!ncrcae!hubcap!gatech!ulysses!cjc
From: cjc@ulysses.homer.nj.att.com (Chris Calabrese[rs])
Newsgroups: comp.windows.news
Subject: Re: Grasshopper psterm
Summary: fast redraw
Message-ID: <10859@ulysses.homer.nj.att.com>
Date: 15 Nov 88 18:13:33 GMT
References: <10834@ulysses.homer.nj.att.com> <1773@goanna.oz>
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 26

In article <1773@goanna.oz>, ajk@goanna.oz (Alan Kent) writes:
| I have had problems with its screen redrawing. If I get a full page of
| output before it starts to draw it, it seems to just not bother doing
| any output. Quite often I do a ls -l but all I get out is the next
| prompt, or a few lines of output if I am lucky.  I only have 4megs on a
| Sun 3/60 (and NeWS 1.1) so NeWS runs pretty slow (it pages to death).
| When I rlogin to a faster machine its quite easy to get large backlogs
| in output. vi on the remote machines also messes up quite frequently
| (probably due to same reason). I have not tried toggling the
| fast-redraw option yet, but it would be better if psterm worked properly
| in the first place.

The problem your're having is definitely with the fast-redraw
algorithm.  We've found that the fast-redraw works really well
when you receive a very large ammount of input very quickly (like
'cat /etc/termcap').  In these instances it simply draws random
gargabe until things have died down, then it correctly draws
the last screen.

When things come in slow enough to have it trip in and out of the
fast repaint mode, you have problems such as not drawing all the input,
leaving copies of the cursor around the screen, etc.
-- 
	Christopher J. Calabrese
	AT&T Bell Laboratories
	att!ulysses!cjc		cjc@ulysses.att.com