I guess I have found the problem why javahelp is not showing the TOC when generated from RoboHelp.
Each JavaHelp file has a helpset file with extension .hs. This HS file tell javahelp about the help file structure as to where is TOC file, index file, and other information.
the problem lies in this ,hs file itself.
The problem line is
you need to change this line to
and now try running the javahelp again, you should be able to see the TOC. thats what I did to make TOC appear in javahelp.
Let me know whether this information helps you or not, so that other people can also use this information
many thanks for your reply and helpful workaround.
I just tried to adjust the hs file according to your suggestion, and everything worked fine
I guess that this will help many other users having the same problem. And I hope that with the next RoboHelp patch, this will be fixed.
Thanks for confirming. Good to hear that given workaround is working as expected
I forgot to add a basic point here, RoboHelp by default provides an option to select the javahelp output version, which is by default 1.1.3.
if you change that to javahelp 2.0, then this TOC problem goes away.
go to javahelp SSL properties and change the version option.
Hope this solves the problem in RoboHelp itself, without changing any code.
Thanks for the additional information, but unfortunately the environment of
my customer currently does only support 1.1.3 (I am creating a
context-sensitive help that is embedded into their application). Thus, I
cannot use JavaHelp 2.0.
But anyway, many thanks for this info.
Praful may have finished for the day so I hope he will not mind me stepping in. I think his point was that instead of making the code change by editing the HS file, if you select the 1.1.3 option in the dialog, RoboHelp will write the correct code for you.
See www.grainge.org for RoboHelp and Authoring tips