Hello, I'm hoping someone can help me with this...
I have a master project and five slave projects. I've created a merged TOC using the "Select Flare Project and Target" option in the TOC Editor in the master project. Fine.
The problem is that in the compiled CHM, when you click on the top level TOC entry for a merged CHM, it does not automtaocally open the required topic. Instead, the TOC entry acts as a container, which means the user must go a level below to get to the topic information. I'm sure there must be a way of linking a top level TOC entry to a startup topic in an external CHM - am I missing something obvious?
Lucy
Linking a merged TOC entry to a topic
Re: Linking a merged TOC entry to a topic
Lucy, I have this problem also - and I feel like I'm missing something! I thought I might be able to drop intro pages for each sub project into my master project TOC, then link those to my 27 sub projects (external help systems). Apparently it's either/or: master project TOC entries can either link to topics in the master project, or to external help systems - in which case, clicking on the TOC entry in the web help output simply expands the TOC, requiring the user to click on the first sub/TOC entry to see the first page of the sub project.
Does anyone know if linking master project TOC entries to external help systems without the weird nesting issue is something that can be done in Flare 3.1 (or in 4.0, for that matter)?
Thanks!
Does anyone know if linking master project TOC entries to external help systems without the weird nesting issue is something that can be done in Flare 3.1 (or in 4.0, for that matter)?
Thanks!
--rose
Re: Linking a merged TOC entry to a topic
I had the problem in 3.1, but it looks like it may be fixed in 4.0.
I haven't upgraded yet, but this is from the 4.0 release information:
"Previously, when you merged projects using a master table of contents or browse sequence, the link entry in the TOC always became a book in the merged output. The content from the child project was placed under it. Starting with this release, you have the ability to replace that entry with the merged content or to let a new book be created from it."
Lucy
I haven't upgraded yet, but this is from the 4.0 release information:
"Previously, when you merged projects using a master table of contents or browse sequence, the link entry in the TOC always became a book in the merged output. The content from the child project was placed under it. Starting with this release, you have the ability to replace that entry with the merged content or to let a new book be created from it."
Lucy
Re: Linking a merged TOC entry to a topic
Looks like we both have good reason to upgrade! Thanks, Lucy.
--rose
-
Ken Billing
- Propeller Head
- Posts: 55
- Joined: Mon Dec 17, 2007 11:33 am
Re: Linking a merged TOC entry to a topic
This may be fixed now in Flare 4 when you link to a project, but it doesn't appear to be fixed if you link to another TOC in the same project. That's is, given TOC entry (link) Z in TOC 1 linked to TOC 2, top level TOC 2 entry A becomes a book below Z instead of in place of Z. This makes Z an empty book without text and the user must open TOC 2 entry A to reach the first topic.
Anybody know a workaround?
Code: Select all
TOC 1
|_Link Z
|_Topic A
Instead of
TOC 1
|_Topic A