You can use BugHunter to identify map numbers and window-level Help topics being called from the application. This is useful if you want to verify that the correct map numbers are assigned to your topics.
Note: The window-level Help topics you test must be compiled into a Microsoft HTML Help file (.CHM) and the application needs to be programmed to use the HTML Help.
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 the window-level Help topics and their aliases are included in the .CHM file. Copy this file into the same folder where the application resides.
Enable BugHunter.
Start the application you need to test.
Arrange your work area and resize the windows so that you can see both the application and BugHunter.
Open a dialog or window that you want to test.
Click the Help button or press F1.
If the application is making the correct call, the correct Help topic opens in a window (either a custom window that you created or the default window). This indicates that the application is calling the correct map number.
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 alias is not working properly. See Troubleshooting context-sensitive Help for assistance.
Tips: |
|
|
|
|
|