TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:Re: Refresh vs Update From:David Eric Dahl <ddahl -at- HARP -dot- AIX -dot- CALPOLY -dot- EDU> Date:Tue, 11 Apr 1995 00:54:34 -0700
Some programs that are extremely graphics-intensive don't immediately
update the screen. This is so that the change being made by the user can
be finished before the screen is updated.
The alternative in some cases would be almost constantly waiting for the
screen to update, a serious hindrance for the user.
Now that graphics systems are so much more efficient than several years
ago, most programs instantly update, and require far greater graphics
resources (1-4MB video cards are standard in PCs now).
