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.
I'm documenting version 1.0 of an application that is
going out to our users in about a month.
Over the last 2 weeks, I've been sending emails to the
developers regarding bugs and usability issues, and
I'd guess that of the approx 15 points that I've
issued to the developers, about 10 of them were
accepted and are being incorporated into the software
and about 5 of them were based on my misunderstanding
of the application or user environment. I've gotten 0
"yes you're right, but we're not going to do it."
(way-cool!)
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?
Before I make this suggestion, I want to make sure
that I'm not mistaken.
Thanks
===
John Posada
Western Union International
(w) jposada -at- westernunion -dot- com
(p) john -at- tdandw -dot- com
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
