If you are testing aliases manually, you need to have access to the application. Follow these suggestions:
If you auto-generated the map files in RoboHELP, give a copy of these files to your developer so the application can be updated to use the map numbers. If your developer provided you with the map files, the application is already coded to use the map numbers.
Compile your HTML Help system so the .CHM includes the aliases (.ALI file). Provide your developer with the .CHM file.
If you designed a custom window for displaying window-level Help, inform your developer at the same time you supply the .CHM file. The application requires coding so it displays the topics in this custom window.
Install the latest version of the application you are testing (this version should use your latest .CHM file). If you install the latest builds of your application from a network drive or CD, you can replace the existing .CHM with the new copy whenever you compile. Copy the .CHM into the same folder where the application’s .EXE file resides.
Print a copy of the Map IDs report. You can use this as a check list when testing each dialog. It lists each topic ID and its matching map number, and indicates if the topic is a text-only popup or an alias (for window-level Help topics). You can also customize the Topic Properties report so it lists the topic IDs, map numbers and map files used with your window-level Help topics.
Invoke the application and open a dialog for which you created a window-level topic.
Click the Help button or press F1. The topic is displayed. If you created a custom window, the topic should be displayed in this window.
Open each dialog box that provides help and verify that the correct Help topic opens. Be sure to try all dialogs. Also, don’t overlook Help menu items and message boxes (if your program uses them). Mark each topic in the Map IDs report as you test.
If you encounter any problems, note which topics are not working properly so you can fix them.
When you finish, open the HTML Help project and update the aliases that did not work properly. Compile the project and then copy the new .CHM file into the application folder and retest the topics that did not work to verify that they are fixed.
Tips: |
|
|