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:Re: graying out part of a graphic From:techielmb <techielmb -at- yahoo -dot- com> To:Paul Pehrson <paulpehrson -at- gmail -dot- com> Date:Thu, 26 Oct 2006 08:36:25 -0700 (PDT)
I did this once a few years ago, and the service techs
and customers really liked it. I just couldn't
remember how I did it!
It's screens on machinery, which makes it a different
type of audience. Maybe that is why they like it,
while an average computer user wouldn't like it. The
screens that I'm putting in the manual include tables
that tell what each button on the screen does. But,
with 30 buttons on a screen, the table gets very long
and spans several pages. This way, I can do just a
chunk of buttons at a time, and the table describing
them can fit on the same page or the facing page.
--- Paul Pehrson <paulpehrson -at- gmail -dot- com> wrote:
> Interesting. I misunderstood your question. Now that
> I see what you were
> asking, I want to point out that I think that you
> *may be* doing your users
> a disservice when you include screen shots that
> don't look like how the
> users' UI will actually look when they are
> performing the same operation.
>
> Depending on the technical aptitude of your
> audience, some users might be
> confused by having all other buttons in the
> documentation appear to be
> inactive, when their buttons on their screen are
> active.
>
> And, as was mentioned by somebody else, it is a
> time-intensive process that
> you have to repeat every time an element in the UI
> changes.
>
> Would it be better for your users to just show the
> button set they will be
> working with and crop the rest of the buttons out of
> the picture? (That is a
> real question; only you can answer this, because
> only you know your app and
> your audience.)
>
> Just a thought.
>
> Best wishes,
>
> Paul Pehrson
> Midvale, UT
>
> On 10/26/06, techielmb <techielmb -at- yahoo -dot- com> wrote:
> >
> > Thanks to everyone for your suggestions. Before my
> > post even made it to the list, I found something
> that
> > works well in my situation. (Isn't that the way it
> > goes, all you have to do is ask the experts and a
> > solution manifests itself. ;)
> >
> > I select the part of the screen I want to show,
> then
> > invert the selection, and use
> Filter>Sketch>Photocopy.
> > The buttons on our screens have graphics, not
> text.
> > There are a lot of colors, but the background is
> gray,
> > so the white background of the Photocopy filter
> works
> > great.
> >
> > Thanks again for your suggestions!
> >
> >
>
> --
> Paul Pehrson
> Midvale, UT
> www.paulpehrson.com blog.paulpehrson.com
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-