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.
Thank you for your input. Wow, I was really starting to question my skills and range of knowledge in technical writing, which I have been immersed in for over 20 years. I was quite tired yesterday as it was Friday around 3:30 when they popped into my cube with this revelation. Here's my analogy: It would be like parking the golf cart and driving a Maserati (full of golf clubs wherever they might fit) full speed on a golf course between holes. No.
From: salt -dot- morton -at- gmail -dot- com
Date: Sat, 11 Apr 2015 12:16:26 -0700
Subject: Re: Using Auto Screen Shot Tools ~ Are They Helpful?
To: jill -dot- gallagher -at- outlook -dot- com; techwr-l -at- lists -dot- techwr-l -dot- com
Your present procedure is the only one that's viable.
On Fri, Apr 10, 2015 at 4:04 PM, Jill Gallagher <jill -dot- gallagher -at- outlook -dot- com> wrote:
Today a project manager (and an IT guy) approached me, all excited about a Microsoft auto screen shot tool she just learned about that will really be beneficial to me and revolutionize my job as a technical writer (who knew?) She wanted me to drop what I was doing and look into it with them immediately at my desk. I did rebuff them, as I was deep in an editing project and I was annoyed, I admit. I'll look into it next week, I told them.
I've never used an automated screen shot tool (static screens, not video) and I don't see the value of "whipping" through an unfamiliar software process in order to quickly create a bevy of numerically named screen shots in a folder. I would still need to revisit each one, rename it, edit it (cropping, etc. as needed), plunk it into my document, and write a draft of the steps associated with it.
My current process is to navigate through the software, digesting the material as the "user," while stopping to create each screen shot using Snippit (that's what we have here). This method allows me to name and save the screen shot and insert it into my document on the fly. I find it especially helpful if I'm learning the software as I go, which is usually the case for technical writers. That's part of our job. In addition, part of my job is to evaluate the user interface and find bugs. My turtle process suits me better than that of the hare. It's more thoughtful and thorough it seems.
Also, can auto screen shot tools capture dropdown menus?