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:what to call a button From:Sharon Burton <sharonburton -at- EMAIL -dot- MSN -dot- COM> Date:Tue, 28 Jul 1998 14:32:20 -0700
I am documenting a product that the client bought from another company with
the limitation that they can only extend the product. They cannot change
what exists.
One of the things that exists is a button that is a picture of a stop sign
or a green light, depending on the state of other things. The tiny little
text (really tiny) on the buttons say Stop for the stop sign and Go for the
green light. The problem is that the tooltip says Run for the green light,
as does the text in the status bar. When the button is mentioned in the
text, it always has a picture of the actual button next to it.
What to do? Is it the Run/Stop button or is it the Go/Stop button? Do we go
with the tiny text or the tooltip? I prefer the tooltip and status bar
because all the other (and there are a lot) buttons are identified this way.
The programmers want Go/Stop since that is what the buttons say.
Changing the interface is not an option.
Opinions?
sharon
Sharon Burton
Anthrobytes Consulting
Home of RoboNEWS(tm), the award-winning unofficial RoboHELP Newsletter
www.anthrobytes.com
anthrobytes -at- anthrobytes -dot- com
Check out www.winhelp.net!
