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.
In the Yes, No, Cancel message box, what would you propose is the reason for
Cancel? Is it that the user made a decision, clicks Yes to accept the
decision, No to discard the decision, and Cancel to . . .?
If you can write a purpose for the cancel button that is different than the
Yes and No buttons, then I'd say you have a case. Offhand, I'd say that not
all message boxes need a Cancel button and, at most, this needs be
determined case-by-case.
Sean
sean -at- quodata -dot- com
>>>-----Original Message-----
>>>From: John Posada [mailto:jposada01 -at- YAHOO -dot- COM]
>>>Sent: Thursday, April 22, 1999 10:43 AM
>>>To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
>>>Subject: Standard presenation
>>>
>>>One of the things that has been nagging at me is this.
>>>
>>>In most applications, when you issue a command that
>>>generates a dialog box with [yes] or [no] buttons, is
>>>it customary to also include a [cancel] button or is
>>>this on a case-by-case basis?
