MadCap Software Forums

I found it. Setting the div.GlossaryPageEntry box width value to 200px accomplished what I needed. I'm not sure what setting that value was inheriting, but at least I know where to control it, now, so I'm adding this for the record.

In the left (navigation) panel of my WebHelp, most settings appear fine -- but, when a glossary term is clicked to show its definition, the definition is much too wide. I believe it is inheriting the standard paragraph width of 800 px that I had set.

I'm thinking that there has to be either ...

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 ...

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 ...

Lisa -- out of intellectual curiosity I tried your suggestion. I was back on track but I wanted to know what had gone wrong. That "process of elimination" solution was just what I needed. I made a copy of the bad CSS and began paring it down.

The problem lines (not immediately apparent when ...

Yes, definitely, Lisa -- all good points.

What I did was to convert the text files to Word; use the Word "compare documents" feature to identify the differences; and locate the styles I wanted to recover. I never was able to identify what was causing the problem (no obvious errant style) but I was ...

Thanks for the suggestions. I'll keep them in mind if it should appear again. In this case, though, it's definitely a corruption of the CSS. If I return to the corrupted CSS, the problem reappears, and changing the mode or medium doesn't "shake" it.

Thinking back ... it first appeared when I was trying to change the output page width for Webhelp. (I was looking at some examples and I liked that look.) I thought it required a body proxy, so I created one. That didn't have the effect I was looking for. Then I realized that I didn't need the body ...

I had in fact introduced a "float" style, Dave. That might be it.

I'm still not quite sure what triggered it, though. I went to a backed-up (but not current) version of my CSS and compared it to the corrupted version (I converted both CSS files to text and compared the text in Word). I still couldn ...

I have definitely narrowed it to the style sheet. If I switch to another, the "edit" mode is usable. But I have spent a lot of time getting the styles as I want them in the working style sheet. What is the gap that I need to fill?

I was incorporating some of the suggestions I had read on this board. Things were going well. I deleted a style I had created, that I realized I had no need for ... and somehow, my design interface has become corrupted.

In the preview and compile windows, all is well. The page width for html is as ...

There are two columns, one row, for a total of two cells. In design, the contents of both cells are positioned at the top (where I want them). In the output, the text in the second cell is still in the second cell but has dropped so that it doesn't begin to appear until below the bottom of the image ...

Thanks, I'll give that a try.

I'd still like to know why a simple table structure isn't being compiled as expected, though. As I noted, it looks fine in design mode; it's the output that's mispositioned.

I have a graphic. I want to place descriptive text to the right of the graphic, as it is rather tall and narrow and space will be otherwise wasted.

The obvious solution, I thought, is a table -- place the graphic in one column and the text in the second column.

On the design form, it looks fine ...

I just reviewed the documentation I've been working on (a Flare project with embedded Mimic movies). I found that, for the Flare (more formal) documentation, I have avoided second-person phrasing -- but, for the Mimic movie inserts, "you" seemed appropriate, as I am addressing the individual who is ...

Okay, I think I have this ... the hotfix contains two files.

WindowsMediaEncoder9
WindowsMediaEncoder9VistaHotfix

The first is the reinstall of Windows Media Encoder. That did not fix the problem.

The description of the second indicates that it is for Vista only. I don't have Vista (I have ...

Same here. I have tried the hotfix posted above, but Mimic is still crashing as soon as I attempt to record. This is also Windows 7, 32-bit.

Very good explanation, Lisa -- thanks.

Here is an example:

http://webhelp.madcapsoftware.com/flare6/Default.htm

Is the bolded heading of "About the Breadcrumbs Proxy" part of the proxy, as it appears to be, or a separate element that is fixed upon the page? Either way -- how can that be accomplished?

I noted that, in your own Help files, the topic name appears to be embedded in the breadcrumbs proxy, rather than in the body of the text. I like the effect because it locks the topic into place (rather than having it scroll out of sight).

I haven't been able to figure out how that was accomplished ...

Yes. Our last posts were at about the same time. I followed some of the links in the earlier post and was able to find a resolution. Thanks for your help.

Just when I think I've found it -- I haven't.

I located the p.MiniTOC1 through p.MiniTOC10 styles and edited those. They look perfect in the Master page preview window.

But when I compile the help, I'm back to the original font colors and styles -- the changes I made to the styles as noted above ...

I've tried changing the Font / Color settings under the miniTOCProxy style, but the only thing that changes is the color of the underline. I think there must be another "list" setting somewhere determining the format values for the text for the various heading entries.

I've found the formatting for the mini-TOC, but there doesn't seem to be anything to impact the links themselves. I know how to create a subclass for the links and their pseudo-classes -- but how can a particular class of links be assigned to the mini-TOC?

Edit -- I gather that there are at least ...

Thank you. Setting "autofit to window," then creating an alternate td class to force the vertical alignment to "text-top" appears to have worked.