Create A Basic WinHelp 3.1 Project FileCreate A Basic WinHelp 3.1 Project File [MAP]
In this section you establish context sensitive help by
associating the *.rtf file footnote(# context string), and the context ID (number)
assigned by the programmer for a given interface or control. A typical entry would look
like this: Contents 100. (See the Basic Help
File page for context string and context sensitive help usage and definitions.)
Note: Microsoft Word macros can be useful tools in making the help
author's lot easier. Case in point, a macro
to retrieve and list context strings from your *.rtf file.
[CONFIG]
Macros and Registrations are entered in this section. Registrations are used to identify
third party tools (*.dll) and Application Program Interface (API) routines. Macros
(sometime in conjunction with *.rtf footnotes) are used to execute predefined commands and
the registration routines. The predefined macros are listed in the Help Compiler Guide.
"BrowseButtons()" is an example of the simplest predefined macro. The use of API
calls within macros is a special case. There is no ready reference; however, a help file
author can find advice and counsel on CompuServe, in the Hypertext Technologies Forum (GO HYPERTEXT).
Note: The order in which macros and registrations appear in the [CONFIG] section can have
an effect on performance, or cause system / program errors; especially if API calls or
third party tools are involved.
[ALIAS]
Alternate Context Strings (Alias) are optional and advanced entries. These strings are
used to assign one or more context strings to the same help topic. The ability to identify
a given help topic by more than one context string is useful when working with revisions,
or for creating complex context sensitive help routines.
[BUILDTAGS]
This advanced section is used in conjunction with *.rtf file footnote (*) and the
[OPTIONS] BUILD entry. The *.rtf file footnote associates a particular build tag with a
given topic. A build tag must be included in the [BUILDTAGS] section and the BUILD
statement, elsewise it is ignored. A build tag may consist of up to thirty-two characters,
in any combination except spaces. Build tags are case insensitive. The [BUILDTAGS] section
may include up to thirty entries.
[BITMAPS]
This advanced section specifies bitmap files to be included by reference in the compiled
help file. However, for most help files this section is not needed. (I have never used
it.) Alternatives include listing the complete path in the *rtf file using the bmX
command; listing the file name using the bmX command and listing the path in the [OPTIONS]
BMROOT entry; or listing the file name using the bmX command, and placing you bitmaps in
the same directory as the *rtf file. (I tend to use this last solution. See the Basic Help File page for bmX usage and definitions.)
[BAGGAGE]
This advanced section specifies files (usually multimedia) to be included by reference in
the compiled help file. For use of this section see the Help Compiler Guide.
 |
| The Freelance Story Teller  |
| Voice: 405 720 7995 |
| Fax: 405 720 7995 |
| 11808 Silvermoon Drive, Oklahoma City, OK 73162 |