Online Help $global_Main / master.chm issue

derrick

Hi Experts,

I'm following the "Walkthrough: Creating and Building a New Help Topic" in the "Help Toolkit" to make sample RTC Help File.
It's working perfectly after some obstacles being fixed. addin_a.chm & addin_a.hh were both produced and they are able be linked to master.chm ($global_Main), click on Help and press F1 both work well too.


:!: Well, whenever I did it with mine one through made a new project of HTML Help Workshop (I named it Ay_a, the final files being produced are Ay_a.chm & Ay_a.hh), the Ay_a.chm file is Unable to be linked up in master.chm, thus it's failed to be called up as Online Help in RTC ..

:?: Does anybody have any clue on in which particular session should I have a deep look into it Or any other suggestions?
I appreciate any ideas. Thank you very much in advance.

lvanvugt

From the heart: all partner projects (to be able to be included in the master project) should be called addin_x.chm with x is a letter from the range a to j.

derrick

From the heart .. haha .. thank you, Luc van Vugt.

a to j, so does that mean only 10 separated .chm we can make?
We've more than 10 in the Classic, is there any workaround other than restructure them into 10 only to be able to have them in RTC?

lvanvugt

derrick wrote:

a to j, so does that mean only 10 separated .chm we can make?

Yes

derrick wrote:

We've more than 10 in the Classic, is there any workaround other than restructure them into 10 only to be able to have them in RTC?

Yes,there is, but I don't know if you want to go that way.
The standard help source are available to partners (on PartnerSource). In this you will also find the the source of the master project, where in the master.hhc and master.hhp is defined what projects - i.e. .chm files - are incorporated in the master.
master.hhc
This is what you find at the end of the long list of incorporated projects in master.hhc:

<OBJECT type="text/sitemap">
<param name="Merge" value="addin_a.chm::\addin_a.hhc">
</OBJECT>
   <OBJECT type="text/sitemap">
<param name="Merge" value="addin_b.chm::\addin_b.hhc">
</OBJECT>
   <OBJECT type="text/sitemap">
<param name="Merge" value="addin_c.chm::\addin_c.hhc">
</OBJECT>
   <OBJECT type="text/sitemap">
<param name="Merge" value="addin_d.chm::\addin_d.hhc">
</OBJECT>
   <OBJECT type="text/sitemap">
<param name="Merge" value="addin_e.chm::\addin_e.hhc">
</OBJECT>
   <OBJECT type="text/sitemap">
<param name="Merge" value="addin_f.chm::\addin_f.hhc">
</OBJECT>
   <OBJECT type="text/sitemap">
<param name="Merge" value="addin_g.chm::\addin_g.hhc">
</OBJECT>
   <OBJECT type="text/sitemap">
<param name="Merge" value="addin_h.chm::\addin_h.hhc">
</OBJECT>
   <OBJECT type="text/sitemap">
<param name="Merge" value="addin_i.chm::\addin_i.hhc">
</OBJECT>
   <OBJECT type="text/sitemap">
<param name="Merge" value="addin_j.chm::\addin_j.hhc">
</OBJECT>

Here you could some more node - let's say k to q - to fullfil your needs.
master.hhp
Here it's somewhate simpler. The section [MERGE FILES] start with:

addin_a.chm
addin_b.chm
addin_c.chm
addin_d.chm
addin_e.chm
addin_f.chm
addin_g.chm
addin_h.chm
addin_i.chm
addin_j.chm

Extend this with your additional projects, for example, k to q.
recompile
You then have to recompile the master project and use the new master.chm and deliver that to your customers.

derrick

Yeah, I could see that probably to the far extent could mess up the whole thing, and probably more things for try-and-error. A further discussion with my colleagues here is a must

Okay, Luc van Vugt, now I got it all, thank you very much! :thumbsup: :thumbsup: