From:	"Graham Reeds" <grahamr AT dtn DOT ntl DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Buffering text...
Lines:	22
X-Priority:	3
X-MSMail-Priority:	Normal
X-Newsreader:	Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE:	Produced By Microsoft MimeOLE V5.50.4133.2400
Message-ID:	<YIgT5.7336$vA4.123021@news6-win.server.ntlworld.com>
Date:	Thu, 23 Nov 2000 22:18:34 -0000
NNTP-Posting-Host:	62.254.80.173
X-Complaints-To:	abuse AT ntlworld DOT com
X-Trace:	news6-win.server.ntlworld.com 975017912 62.254.80.173 (Thu, 23 Nov 2000 22:18:32 GMT)
NNTP-Posting-Date:	Thu, 23 Nov 2000 22:18:32 GMT
Organization:	ntlworld News Service
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I'm trying to blit some text in a dosbox under w98se. The text box is
usually of the 50+ line variety so I can see all that goes horribly wrong
when I compile:-)  However, when I do a text output of the debug info and
variables in real-time, the screen flickers horribly.  I've tried putting a
vsync in there before the clrscr(), but it still flickers horribly.  Is
there anyway of efficiently (i.e. fast) updating the text output while
keeping it readable - the last few lines are almost unreadable since it
takes a while for the update to get down there.  Unfortunately it isn't as
easy as updating just the lines that change since sometimes 50% plus of
variables are changing and so that means most of the screen.  I've also
tried buffering each line to a string and blitting that rather than several
printf()'s per line but that has had no noticeable effect.

Any ideas?

--

Stay Lucky, Graham "Mournblade" Reeds.
ICQ No.:  30514803
http://homepage.dtn.ntl.com/grahamr

- Raw text -