miniTOC depth issue

This forum is for all Flare issues related to PDF, eBook, Microsoft Word, Adobe FrameMaker, XPS, and XHTML book targets.
Post Reply
Leon Descoteaux
Propeller Head
Posts: 29
Joined: Fri Jun 27, 2014 7:51 am

miniTOC depth issue

Post by Leon Descoteaux »

I can't get the TOC depth in a print miniTOC to go beyond the default level 2 (h2's under the h1, where the proxy is placed). The h3's and h4's are being ignored. The settings are:

Right click proxy in the topic > Edit MiniTOC Proxy window
TOC Depth of 4

CSS file > @media print > MadCap|miniTocProxy
mc-toc-depth: 4;

What am I missing?
Leon
formerly User crdmerge and crdmerge2
Nita Beck
Senior Propellus Maximus
Posts: 3672
Joined: Thu Feb 02, 2006 9:57 am
Location: Pittsford, NY

Re: miniTOC depth issue

Post by Nita Beck »

Check the code for the p.TOC3 and p.TOC4 (I think; I'm on an iPad at the moment so am going on memory). What is the mc-heading-level attribute in each set to?
Nita
Image
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
Leon Descoteaux
Propeller Head
Posts: 29
Joined: Fri Jun 27, 2014 7:51 am

Re: miniTOC depth issue

Post by Leon Descoteaux »

Nita, thx for responding.

There is nothing in our CSS for those elements; nor are there any mc-heading-level settings for h2, which does appear in the print mini-TOC.

Does Flare only compile one head level as default, unless you have specifically set levels for each head? They don't say anything in their help (wicked surprise!). :D

Oh, did I mention that the h2's and h3's are in drop-downs, and some in snippets? What could possibly go wrong? :roll:
Leon
formerly User crdmerge and crdmerge2
Nita Beck
Senior Propellus Maximus
Posts: 3672
Joined: Thu Feb 02, 2006 9:57 am
Location: Pittsford, NY

Re: miniTOC depth issue

Post by Nita Beck »

In your target, have you selected the "Use TOC depth for heading levels"? If yes, then you're telling Flare to reassign heading levels to all headings based on the structure of the TOC. So could it be that some of the headings you've set to h3 and h4 in source topics are being converted to h5 and h6 in generated topics and, hence, they are not appearing in your miniTOCs? Just an idea...
Nita
Image
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
Leon Descoteaux
Propeller Head
Posts: 29
Joined: Fri Jun 27, 2014 7:51 am

Re: miniTOC depth issue

Post by Leon Descoteaux »

No, Nita, that option is not selected, thx.
Leon
formerly User crdmerge and crdmerge2
Nita Beck
Senior Propellus Maximus
Posts: 3672
Joined: Thu Feb 02, 2006 9:57 am
Location: Pittsford, NY

Re: miniTOC depth issue

Post by Nita Beck »

I'm at a loss then. Anyone else got ideas for Leon? (Probably when I read those other ideas, it'll be a forehead-slap for me!)
Nita
Image
RETIRED, but still fond of all the Flare friends I've made. See you around now and then!
NorthEast
Master Propellus Maximus
Posts: 6426
Joined: Mon Mar 05, 2007 8:33 am

Re: miniTOC depth issue

Post by NorthEast »

The print mini-TOC will only show items that are included in the print TOC proxy; so if they're not included in the main print TOC proxy, they'll not be in the mini-TOC either. Setting the TOC depth of 4 for the mini-TOC just means show 4 levels from the main print TOC proxy.

So the first thing to do is make sure that your print TOC proxy includes all the headings; i.e. if h3 and h4 aren't included, make sure these styles are being included by setting their mc-heading-level property.
ChoccieMuffin
Senior Propellus Maximus
Posts: 2650
Joined: Wed Apr 14, 2010 8:01 am
Location: Surrey, UK

Re: miniTOC depth issue

Post by ChoccieMuffin »

Hmm... that's not always what you want. I feel a feature request coming on to allow you to have your MAIN TOC showing, for example, just H1 and H2, but allowing mini-TOCs to contain, for example, H2, H3 and H4.
Started as a newbie with Flare 6.1, now using Flare 2024r2.
Report bugs at http://www.madcapsoftware.com/bugs/submit.aspx.
Request features at https://www.madcapsoftware.com/feedback ... quest.aspx
Post Reply