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:Paul David Marvel <marvel -at- STRAUSS -dot- UDEL -dot- EDU> Date:Sat, 8 Apr 1995 10:09:40 -0400
> Do you really mean to say that you have an application that doesn't
> update the screen as changes are made, which you think is geared toward
> non-technical users?
I don't know about the program in question, but this is common. For
example, a sales rep might enter a customer's ID number and product codes
to fill out an order. S/he then presses enter and the program looks up and
displays the customer's name, address, names of the products, an order
number, etc. Something I've seen that works well is to say "press enter to
verify the information." Once they've done this once it becomes