On 5/24/2011 12:39 AM, David wrote:
Well, could definitely agree with you here. Never understood the
logic, for GW to even start out a practice, where they put all the
options and settings for an App under the Help button.
Remember, the button is called Help AND Options, not just help.
OK, you get used to it, but for anyone who first put their hands on
WE, it will not even occur for them to look under HELP, to make any
settings changes.
That's why we came up with the App menu structure.
If GW wants us to put things under that menu, or button, why not
simply change its name to OPTIONS. They changed from scripts, to apps,
to be more in line with general computing terms. Then why not make the
change from HELP, to OPTIONS, to fulfill that change.
The button is designed to give app authors an easy way for users to get
specific information about a running script while they're using the app
manager. It was titled Help and Options to give the user some sense of
direction. Remember, this was back in the day of 7.0, when Window-Eyes
scripting was first born. Most of the time, these days, apps will
provide configuration options and documentation in their respective
entries in the Apps menu. This legacy button still exists for getting
assistance, as mentioned, when navigating through the app manager dialog.
But if you see a help-button, NOONE would ever think of going there,
to look for settings.
Remember, it's called Help and Options, not just Help.
Further, in many cases, if now you decide to go to look for your
settings under that HELP button... Well, where does that take you?
Into another screen, where there is little or no settings.
That is completely up to the app author. Many people use the GW
Toolkit's Standard Help Dialog, but you don't have to. You're free to
design whatever dialog you want. I'm not sure it's clear what the Help
and Options button really does. It doesn't launch a dialog. It calls a
specified routine. What that routine does is up to the author. Whether a
string is displayed in a message box, a dialog is displayed, or some
other completely different function occurs is strictly up to the person
who designs the app. The GW Toolkit offers one possible solution, and
it's one that we use in all GW Micro apps. But, as J.J. mentioned, that
doesn't mean you are forced to use it. Help and Options is a generic
term that gives the app author to ability to do whatever they want. I
don't see what changing the name accomplishes.
Aaron
--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
