Set-up --> Master TOC
+ Merged child CHMs which display master TOC by default and have second window definition with their own TOC listed
Is it possible to display the child via command line stand-alone with its own TOC for testing?
e.g. hh.exe "path\file.chm" SomeSwitch NameOfWindow
Open run-time merged CHM with own TOC
Moderators: Alexander Halser, Tim Green
-
- Posts: 305
- Joined: Mon Aug 21, 2017 7:35 pm
Re: Open run-time merged CHM with own TOC
Ok, so the Test HtmlHelp API dialogue in HTML Help Workshop allows me to do this.
Is there a way to do that from the command line?
Is there a way to do that from the command line?
- Tim Green
- Site Admin
- Posts: 23181
- Joined: Mon Jun 24, 2002 9:11 am
- Location: Bruehl, Germany
- Contact:
Re: Open run-time merged CHM with own TOC
Hi John,
This is a setting in Help+Manual. At the moment you have the child CHM configured to open the master CHM automatically when it is opened on its own. You can change this in the child HM project in Configuration > Publishing Options > MS HTML Help > Extended .HHP Settings.
This is a setting in Help+Manual. At the moment you have the child CHM configured to open the master CHM automatically when it is opened on its own. You can change this in the child HM project in Configuration > Publishing Options > MS HTML Help > Extended .HHP Settings.
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
-
- Posts: 305
- Joined: Mon Aug 21, 2017 7:35 pm
Re: Open run-time merged CHM with own TOC
Hi Tim,
That is correct as it is a run-time merged child which should display the master TOC when called from the application -- which is what is required.
I would still also like to be able to open the child CHM stand-alone with its own TOC. That works via the Test tool -- I was just hoping for a more automated manner.
That is correct as it is a run-time merged child which should display the master TOC when called from the application -- which is what is required.
I would still also like to be able to open the child CHM stand-alone with its own TOC. That works via the Test tool -- I was just hoping for a more automated manner.