MadCap Software Forums

Ah yeah, good question. I'm using the 32-bit version of the plug-in. I can't speak to the 64-bit version, sorry.

Okay, here it is in a brand new (and rather large, I warn you) post on the subject:

http://forums.madcapsoftware.com/viewto ... 68&t=10401

Hope it helps.

Graham

****NOTE: The 6.1 patch resolves the issues I was facing with PushOK in Flare v6. I can confirm the following post now works with both v5 and v6.1****

A couple of people have requested my notes on binding projects to SVN from within Flare using the Push OK plug-in.

There's some preamble to this ...

To tie this one off, I found through talking to those excellent MadCap support bods (specifically Kip and Ryan, to give the proper hat tip) that the issue arose from my PageLayout having multiple Body frames, as opposed to just a single Header, Body and Footer each.

Now, my position on this is that ...

Not sure if you're still looking for help with this one, but I've recently installed Push OK and found it to be very usable.

The issue you're seeing may be because the project thinks it's still bound to the SVN repository, despite the fact that it failed to bind properly. You need to break the ...

I've only very recently been suffering an issue with Flare when opening topics to edit in the XML editor. I see this:
stackerror.png
which is frankly useless information.

This doesn't happen with every topic, and the topics that are affected all seem to be properly formatted HTML (Flare does ...

Turns out there's a patch that resolved this issue for me.

Shame I didn't know about the patch before contact MadCap support by raising a bug, but at least the issue was resolved.

I should also note that when I click "Preview as HTML Help Window" in the Skin Editor, it shows up exactly as I expect it to.

Only in the built CHM does it misbehave.

Also, I should mention we're all using Flare 5 in the office. I just tried rebuilding the help in Flare 4.2 and it works perfectly ...

Incidentally, just to tie up loose ends, I haven't seen this issue occur again for the last couple version of Flare (I'm now using Flare 5 and PDF output works just fine, as does HTML and Web Help).

In the meantime since I last visited this thread, I've been rebuilding our in-house CSS and as a result I no longer experience this problem.

I can only conclude that our original stylesheets (which were over three years old and quite bloated by the time I came to use them) were conflicting in some ...

Thanks Greg, I'd thought as much but it's good to know for sure.

I've submitted a feature enhancement, so here's hoping something will come of it.

G

I have four skins in my project: DefaultWindow, IndexWindow, SearchWindow and ContextWindow. The first three work perfectly.

The ContextWindow skin is used to display our context-sensitive help topics, when users press F1 or the associated Help button on modal dialogs in our application. It isn't ...

I'm trying to use the Glossary Term Link functionality to actually link to the term in my glossary, but using any text I want rather than the glossary term itself.

So for example, I might have a term "field" with a definition that I want to be linked to from the word field in the sentence:

"Data ...

Still not working.

None of my heading styles comply with this, whereas other paragraph styles do (such as the titles of procedures or Note and Important boxes).

Quite confused about this one. page-break-after: always; does work. page-break-before: always; also works. page-break-after: avoid; never ...

Bonnie wins the top prize. I did not know about the change of style use if Use TOC depth for heading levels is selected, so that was one part. Turned out to be a combination between that and the page-break-after: avoid style which I also had set.

Seems to me to be a bit odd that setting the page ...

Nita,

Yes I do see what you're getting at, but unfortunately what you describe isn't quite the issue I'm suffering. Every entry, be it TOC1, TOC 2 or whatever, is printed on a new page until the last full page of properly formatted ToC content.

Going through this some more, I'm pretty convinced it ...

UPDATE

I've been going back through this doc after a break away from it and I noticed that the single line issue only happens when my ToC stretches to more than a page. If I remove enough content such that the ToC fits in a single page, then it formats perfectly.

As soon as I add in enough content ...

It's defined once only, but you're right - it is good to check these basic things.

G

I have set the Page Break After property in each of my heading styles (H1 to H6, as well as a couple of classes of H1) to Avoid, yet Flare only occasionally sets the correct behaviour in the PDF output. The rest of the time I get this:

break-after.png

That shows my H2 and H3 styles, with the ...

Lisa's suggestion is solid. Look at your TOC styles (TOC1, TOC2, TOC3, etc.). Is it possible one of these styles includes "page-break-after: always" or "page-break-before: always"?

None of my p.TOC1 etc. styles have any of the page-break attributes (before, after or inside) set. Surely though, if ...

This looks like a page layout problem.

The left (even) page of the layout being used for the TOC might be faulty. The right (odd) pages look fine, right?

Afraid not, no. The page numbers on display in the attached images are just chance and not indicative of a difference in the page layouts ...

I have about 25 pages of this rubbish:

wrong.png

followed by a single page of this, which is what I want:

right.png


Some more info:

I'm using a TOC proxy, and my understanding is that the styles are picked up for the TOC overall from the TOC.proxy style.

None of my pTOC styles have page ...

My target is printing to a PDF, and my TOC file is using a TOC proxy.

The problem I'm seeing is the TOC is printing approximately half the TOC entries as single lines on new pages (around 20 of those) and then prints the other half as you would normally expected, all leveled and grouped together ...

I stand corrected and happily swallow my pride to admit it was a CSS issue.

Richard, I'm in your debt. Thanks so much for resolving this for me. MadCap service at its best!

As I suggest in my original posting, the Web layout is just as horrible - see the attached for visual aid.

Most of my docs are for printed formatting so working with the Web layout wouldn't be beneficial for me even if it did render properly. I'll check through the Flare docs as you suggest to see ...