Hi all, we used to display the TOC of the master project when any of the merged sub-CHMs are opened. For this, in the merged projects it was necessary to point the advanced properties of the window to the hhc of the master, e.g.:
What version of RH are you using. There was an issue with absolute path names in RH9 although this was fixed in a patch. Also ensure you have no blanks or underscores in your CHM file names.
I am using the current version RH 11, the file names do not have any blanks or underscores in them. I also created new test projects just named 'master', 'alpha', 'beta' etc to test merging and the problem remains.
I am afraid I gave up using merged CHMs many years ago before Win 64 came along so do not know what more I can add t this thread. It maybe worth trying to compile the master using the Microsoft HTML Help workshop to see if that makes any difference.
Using the HTML Help Workshop sems to work! However, I cannot compile the RH project directly because the topic files ar not clean HTML. So I have to compile a CHM first, then decompile this and copy the hhp file from the Robohelp project into the decompiled files. Then, using the HHW I compile it again.. the result does work out (the master-TOC appears in the merged sub project) but I think the effort might be too high.
I spoke too early - the master TOC is only displayed when the merged CHM is opened directly (by double-click). When I open the merged CHM using a context call via map number, the correct topic is displayed but no TOC at all.
I used the window name "$global_standard" in all help projects. Is this a problem? I though this naming is necessary.
When I call the merged project with a map number, then the window opens correctly, also the correct topic is displayed. The TOC tab is completely empty (white space).
This is very strange, because if I open the very same CHM by double-clicking then the TOC is present..
7
Replies
AdChoices