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.
>To me, the word "select" can be (mis)construed as simply setting the
>focus to the button, not actually activating it (as in "select the
>button to be relocated and drag it to the new position" ...an example
>off the top of my head).
I refer to "selecting" a command, not a button. I also refer to "clicking"
on any GUI item that can't be "selected" by a keyboard. For example:
Click and drag the scrollbar until the <foobar> command is visible. Once
"OK" is selected, the <foobar> command executes with the defaults in
the <foobar> options window."
I'm probably not consistent with this, and I'm not sure it works for
everyone. It works well in my situation.
David (The Man) Blyth
Technical Writer
Alsys (San Diego)
dsb -at- alsys -dot- com
My opinions are not necessarily those of my employer (but they should be).
