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.
The button label issue is tricky, now that you can have
two or three button 'meeces' as well as little guys with
trackballs.
Just off the top of my head, maybe 'primary' and 'secondary'?
Or 'activate' and 'option'? Regardless, if your customers have
the option of reconfiguring button function, you cannot reliably
predict which button will do what since the user may have
altered the default functionality of the mouse buttons.
If your software is Windows-based, I would use the L and R
solutions, telling your users that button instructions assume
that they have not reversed Windows' default configuration and
warning them that if they *have* flopped the default,
they must interpret all button instructions appropriately.
Anne Halsey
senior tech writer, StorageTek
anne_halsey -at- stortek -dot- com
