You can use BugHunter to find out if your window-level Help topics are using the correct map numbers, even if the application is not available. The window-level Help topics you test must be compiled into a Microsoft HTML Help file (.CHM).
Before you start, print a copy of the Map IDs report. Use this report as a check list for testing each window-level Help topic. It provides you with a list of all topic IDs in your project. Grouped with each topic ID is its map number, the name of the map file that uses it, and the name of the window-level Help topic (.HTM file).
Compile your HTML Help project so all window-level Help topics and their aliases are included in the .CHM file.
Right-click inside the BugHunter window and select Test HtmlHelp API.
Select the compiled HTML Help file (.CHM).
Click to locate the drive/folder where
the .CHM file is located and double-click to select it.
From Command, select HH_HELP_CONTEXT. This is the HtmlHelp API command that BugHunter uses to capture information about window-level topics.
In Window, enter the name of the custom window you designed for your window-level Help topics. (The developer needs to program the application to use this window.) BugHunter will display the topics in this window as you test each one.
Skip this step if you did not design a custom window. BugHunter will use the default window to display the topics.
In Map Number, enter the map number to test. The Map IDs report shows which map number is used with each window-level topic. Use this for quick reference.
Click Test.
If the correct Help topic is displayed in the correct window, the correct map number is used. The application will call this same map number when users ask for help about the dialog or window.
BugHunter displays the .CHM file name, map number, and the .HTM file name for the topic. For details about information displayed in BugHunter, see Interpreting window-level Help data.
If the wrong window is used, the wrong topic opens, or the Help topic does not open, error messages will indicate that the map number is not working properly. See Troubleshooting context-sensitive Help for assistance.
Tips: |
|
|
|
|
|