I am testing using the auto-generate feature in the Table of Contents to add a level of entries to the on-line ToC. That's working fine. The problem is that the section I tested that on, does not share the appearance of the others. Specifically, there is a wider border around the body window (I can live with that). A bigger concern is that the page width settings I had established, are being ignored for that section. I had successfully set the body with to 800 px using the Madcap style settings - Madcap|BodyProxy: 800 px. (The window is a full window -- too wide to read easily. That's why I narrowed the body.)
All other sections look fine; it's just the section with the auto-generated entries in the TOC that seems to be obeying other settings for width, etc., and filling the window edge to edge. What additional settings control the body width when the section's TOC is set to use auto-generate for headings? It seems the section has gone into some other mode ...
Auto-generate in TOC changes display
Auto-generate in TOC changes display
Judy Hennessey
Re: Auto-generate in TOC changes display
My first reaction is that I wouldn't have thought the two things were related.
If you switch off the auto-generate for that topic in the TOC, does the topic look ok when you build the help, or is it still wrong?
Possible reasons that your topics might look different are if they are using different stylesheets, different master pages, or contain any inline styles (on the body tag).
Also, do you have a width setting for the body tag in your stylesheet?
If you switch off the auto-generate for that topic in the TOC, does the topic look ok when you build the help, or is it still wrong?
Possible reasons that your topics might look different are if they are using different stylesheets, different master pages, or contain any inline styles (on the body tag).
Also, do you have a width setting for the body tag in your stylesheet?
Re: Auto-generate in TOC changes display
They definitely are connected, Dave. Simply unchecking the "Compute auto-sub entries from linked file" option for the selected section in the ToC returned the page itself to proper width.
I tried setting the "Open in Skin" property (under Advanced) directly to the target skin, which I am not crazy about -- I've been using a common ToC for two different brandings -- but that didn't fix the problem, so I switched it back to (default). There is no option to point a ToC entry directly to a stylesheet, and in any event, I am using a common stylesheet for both targets.
Next, I tried setting the stylesheet and setting the "p" width to 800px. That improved things -- but, wherever there was a min-ToC proxy appearing in the footer, THAT was now corrupted (bad width; snippet with company and copyright information pushed off to right and too narrow. So I hard-coded the width of the Madcap|miniTocProxy to 450px.
A bit closer still -- but any paragraph following a style other than "p" that appeared in the section with the auto-generated headings was still too wide. I had to go to each list or note paragraph style and lock it in at 800px. So far, it's looking good -- but none of the above should have been necessary. Until I tried to auto-generate headings, the one setting under the madcap|BodyProxy had been sufficient to control the width of the page and footers.
All of this, because that one checkbox for auto-generate heading throws the page into a different mode. I still haven't figured out why the border is wider. I still believe that the bodyproxy setting is not applying when auto-generate is checked. If I knew what WAS applying, I'd have gone directly there.
I tried setting the "Open in Skin" property (under Advanced) directly to the target skin, which I am not crazy about -- I've been using a common ToC for two different brandings -- but that didn't fix the problem, so I switched it back to (default). There is no option to point a ToC entry directly to a stylesheet, and in any event, I am using a common stylesheet for both targets.
Next, I tried setting the stylesheet and setting the "p" width to 800px. That improved things -- but, wherever there was a min-ToC proxy appearing in the footer, THAT was now corrupted (bad width; snippet with company and copyright information pushed off to right and too narrow. So I hard-coded the width of the Madcap|miniTocProxy to 450px.
A bit closer still -- but any paragraph following a style other than "p" that appeared in the section with the auto-generated headings was still too wide. I had to go to each list or note paragraph style and lock it in at 800px. So far, it's looking good -- but none of the above should have been necessary. Until I tried to auto-generate headings, the one setting under the madcap|BodyProxy had been sufficient to control the width of the page and footers.
All of this, because that one checkbox for auto-generate heading throws the page into a different mode. I still haven't figured out why the border is wider. I still believe that the bodyproxy setting is not applying when auto-generate is checked. If I knew what WAS applying, I'd have gone directly there.
Judy Hennessey