Copy link to clipboard
Copied
My merged slave .chm file is not showing up in the master .chm file after generation. Anyone seen this happen before?
Ahhh, a plot twist I see!
Yeah, there was a thread a day or three back where someone was trying something similar.
Click here to view that thread
Cheers... Rick
Copy link to clipboard
Copied
Is the child CHM in the same folder as the master CHM? Does the child CHM have a TOC with topics?
Copy link to clipboard
Copied
Yes, the child CHM is in the same folder. Also, the child is a fully functioning CHM with a TOC with topics. It is an existing Security help file that we are attempting to embed into an Application help file to prevent having to send two separate files.
Copy link to clipboard
Copied
Hi there
Some screen shots might be helpful here.
1. Shot of the Master TOC
2. Shot of the Windows File Explorer view showing the CHMs together
Cheers... Rick
Copy link to clipboard
Copied
No problem. Just a bit more information as well.
I have found that when I generate a normal chm file, the merge works. But, when a do a webhelp to chm output, it does not. Also, this behavior is happening in 11 and 2015.
Here is the TOC in my master project:
Here is the generated TOC from the CHM file if I use the normal Microsoft HTML Help output option.
But, if I do the webhelp to chm output, the child chm file topics are missing:
Copy link to clipboard
Copied
Ahhh, a plot twist I see!
Yeah, there was a thread a day or three back where someone was trying something similar.
Click here to view that thread
Cheers... Rick
Copy link to clipboard
Copied
Never heard of the WebHelp to CHM option, but looking into it a bit leads me to believe that the only way it would work would be to do your merged projects first as WebHelp, then run the WebHelp to CHM converter; again, I agree with Rick – Adobe may have never considered that scenario…