RE: Another Newbie question about procedures

[hanac -at- worldnet -dot- att -dot- net]

Hello,
I'm in agreement that the documented task flow needs to be completed to
avoid confusion. However...is the task flow actually completed by clicking
the OK button? [I'm more interested in the dynamics of OK than the other
buttons].

Here's my question about the task flow:
By clicking the OK button, are you merely 'confirming' your settings, or
are you activating the settings? And if the answer is 'confirming only,'
is there another step after 'confirming' [such as, for example, a 'use
settings' or 'activate settings' option from something like a File menu at
the top menu bar] ?

To address the redundancy issue...
If all dialog boxes for your product are functionally identical at the OK
and Cancel buttons, and the OK button is always the way to set your
configuration in motion, I would write it only into the 'tools' section at
the beginning of your manual, and forget about it throughout the
individual task sequences. But to do this, I recommend that you ensure
it's clear in the TOC and the index where user can find info about OK and
Cancel buttons.

Best of luck!

hana




 




^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

New from Quadralay Corporation: WebWorks ePublisher Pro!
Completely XML-based online publishing. Easily create 14 online formats, including 6 Help systems, in a streamlined project-based workflow. Word version ships in June, FrameMaker version ships in July. Sign up for a live, online demo! http://www.webworks.com/techwr-l

---
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot-  Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.