 | ||
|
| ||
| ||
|
| ||
Microsoft Corporation
Updated: September 8, 1998
How can I use Visual Basic with HTML Help?
What files need to be distributed with my compiled HTML Help (.chm) file?
What if my user wants to use a browser other than Internet Explorer?
Why can't I read the text in my Help file when using Windows 98?
Why is there an "X" where my graphic should be in my help topic?
Why does HTML Help Workshop sometimes "hang" when I edit the [ALIAS] and [MAP] sections?
Why don't my graphics print when I print all topics under a heading?
Is there a registry key that enables me to find out if HTML Help is set up on my computer?
How are full-text search hits ranked?
How do I link from a WinHelp topic to an HTML Help topic?
What files make up the HTML Help client? Where are they installed? Are they registered?
What's the best source of documentation for HTML Help?
Is HTML Help always going to be free on the Web?
Do I need Internet Explorer to use HTML Help?
Using WinHelp I could create a formatted pop-up window. How can I do this in HTML Help?
Is it possible to open a specific topic from the Hh.exe command line?
How can I make the HTML Help window remain even though the calling process has been terminated?
There are several Microsoft Knowledge Base articles about using Visual Basic with HTML Help. The following is a partial list of available topics with article ID numbers:
To locate one of the above topics, on the Microsoft Knowledge Base search page 
, select the Specific article ID number option, and then type the ID number in the box. To see all of the articles related to HTML Help, search the Microsoft Knowledge Base for the phrase "html AND help."
The HTML Help Installation and Update package (Hhupd.exe), your compiled help file, and if Internet Explorer is not already set up on the user's computer, Microsoft Internet Explorer (version 3.02 or later). Hhupd.exe can be found on your local drive, in the HTML Help Workshop\redist directory. You can find out more about redistributing Microsoft Internet Explorer at http:/ /www.microsoft.com/windows/ieak/en/default.asp .
Yes.
They can continue to use any browser they want. However, the HTML Help Java Applet, which is supported across browsers, only works with a subset of the navigation features supported by the HTML Help ActiveX control. The applet supports:
If Windows 98 is configured to use the high contrast black color scheme an end user may not be able to read the text in Windows Help. The background will blend closely with the color of the font. An end user can fix this problem in the following way: Go to the Control Panel, Internet, Click General, Accessibility, and then click the Ignore Colors Specified on Web pages.
Help authors can help prevent this problem by not shipping a style sheet (.css file) or in line styles where the background color is defined as white.
This usually means that your graphics file cannot be found. Check the path.
There is a bug that makes the editing of these sections very unstable. If you have trouble editing them, use Notepad (Notepad.exe) or another text editor to open your project (.hhp) file, and then edit the source.
The compiler will pull in topics referred to by HREF and SRC attributes. It will report any missing files in the error log. Referring to files through script or Dynamic HTML (DHTML) tags is not supported and those files will have to be manually added to the [FILES] section of your project (.hhp) file.
Internet Explorer cannot open the Internet site mk:MSITStore:c:\<path>\<project.chm>::/default.htm.
An unexpected error has occured.
What does it mean?
HTML Help instructed Microsoft Internet Explorer to look for a particular file within the compiled help title, and it couldn't be found. You should have received an error when you compiled your project (.hhp) file warning that a file was missing, or that no default file was specified.
If you don't specify a default file in your project options, HTML Help will attempt to open Default.htm (but there shouldn't be a path). Please note that default files must be set for each window you define. If you are not using window definitions, then the default file must be specified in the Project Options dialog box.
This is a known bug. It will be fixed in a later release.
You can look for the CLSID of Hhctrl.ocx in HKEY_CLASSES_ROOT\CLSID. The CLSID is:
ADB880A6-D8FF-11CF-9377-00AA003B7A11
This key is registered by the system during setup.
This work has been delayed until the next major release of HTML Help (2.0) which will be COM+ based.
You need to install DCOM95 version 1.2 for Windows 95. You can download it from http://www.microsoft.com/cominfo/dcom95/ .
For a single compiled help (.chm) file, results are ranked by the number of hits within each topic (the number of times the search term is found within a topic). For a multiple-title help system, it's a little more complex.
If you have, for example, 5 compiled help files in your help system, the top-ranking hit from each title will be listed, followed by the second-ranking hit for each title, followed by the third, and so on. This process is followed until all the results are returned, or a total of 500 topic titles are listed.
It is not easy to remove Hhctrl.ocx because it is considered to be a system component. To remove your current version of Hhctrl.ocx and install an older version, type the following from the command line:
Now that you have removed the newer run-time components, you can get the older components by installing either an older version of HTML Help Workshop, or an older version of the HTML Help Installation and Update package (Hhupd.exe).
The Match similar words option uses Western-language rules for determining suffixes and finds all occurrences of a given word that include common suffixes. For example, a search for "run" will find words such as "run," running," and "runner." The word "runtime" will not be found.
Here's the correct syntax for jumping from a WinHelp topic link to a topic in a compiled HTML Help (.chm) file:
!execfile(hh.exe, filename.chm::/topic.htm)
where !execfile is the name of the WinHelp macro, hh.exe is the HTML Help executable program, filename.chm is the name of the compiled help file, and topic.htm is the name of the HTML topic file.
The client files are:
Full-text search highlighting.
Your compiled help files will work with new versions of the Help Viewer and you will be able to create compiled help files with new versions of the workshop that will work with older versions of the Help Viewer.
Aside from the general information contained on this Web site, the best source of documentation for HTML Help is the help that ships with HTML Help Workshop. Set up HTML Help Workshop, click the Help menu, and then click Help Topics.
The Microsoft Press book, the Official HTML Help Authoring Kit is also a good source of information. Updated companion files, information about how to set up the sample programs, and other late-breaking news about this book is available from the Microsoft Press Web site .
Yes, that's the plan.
The HTML Help ActiveX control requires that Internet Explorer be set up on a user's computer. HTML Help works with Microsoft Internet Explorer 3.02, but to take advantage of the full functionality of HTML Help, you should use the latest release of Internet Explorer. HTML Help does not require that you use Internet Explorer as your default browser.
Internet Explorer 4.0 or later is needed to get highlighting of full-text search terms, to get the auto-underlining and auto-expand/collapse of the table of contents, to be able to access compiled HTML Help (.chm) files over a Hypertext Transfer Protocol (HTTP) connection, and to be able to display some multimedia file types (such as AVI) within a compiled help file. In addition, anything authored on an HTML page that takes advantage of Dynamic HTML (DHTML) will work only with Internet Explorer 4.0 or later.
For now, HTML Help supports only simple text-only pop-up windows with no formatting. For more sophisticated formatting you need to use regular HTML-based topics instead of pop-up windows. Alternatively, you can continue to use WinHelp for your pop-up windows.
Yes, try:
hh mk:@MSITStore:/path/filename.chm::/path\topicname.htm
For example, with the compiled help file htmlhelp.chm, you can use:
How can I make the HTML Help window remain even though the calling process has been terminated?
There is more than one way to solve this problem.
HTML Help is implemented as a DLL and is, therefore, always in-process. It terminates when the process that creates it terminates. To keep HTML Help around, the process that creates it must stay around.
One way to do this is to create an executable (.exe) file that calls HTML Help. This .exe file should stay running until HTML Help is closed by the user. You will also have to implement a method for communicating between this .exe file and the executable file of your program.
Another solution is to load your title under Hh.exe. If you WinExec your title, then the standard Windows file association code will load it using Hh.exe and it will remain running until the user closes Hh.exe.
There are several key limitations to using embedded windows. This is because an HTML Help window is not designed to be a child window of an application. Control over the appearance of the help window is somewhat limited, and painting/resizing of the window is unpredictable. In addition, you will have to run Hhctrl.ocx in single-threaded mode. The following topic explains the problem and its solution in detail:
To locate the above topic, on the Microsoft Knowledge Base search page , select the Specific article ID number option, and then type the ID number in the box. To see all of the articles related to HTML Help, search the Microsoft Knowledge Base for the phrase "html AND help."
Did you find this material useful? Gripes? Compliments? Suggestions for other articles? Write us!
© 1999 Microsoft Corporation. All rights reserved. Terms of use.
Back to top