MadCap Software Forums

In working with many Flare clients over the years, I will say it is very rare that I recommend people use multiple style sheets to deal with media types. It adds an unnecessary layer of complexity for marginal benefit for most people. Especially since in later versions of Flare you can have display ...

Ditto what Dave said. Don't modify this in the program files folder. The best solution is to just replace it in the skin, following Dave's instructions. It does not need to have the same name. When you select the replacement icon, Flare will update all references to the file name and will use the ...

MadCap has a whole guide around how to do context-sensitive help. You can find it here:

http://docs.madcapsoftware.com/flare201 ... HGuide.pdf

Welcome to the forums! Hope this gets you pointed in the right direction. If you have more questions, please don't hesitate to ask.

Make sure the style declaration is div.indent, not just indent.

Either of the following will work:


div.indent {
margin-left:100px;
}


.indent {
margin-left:100px;
}

According to your screen shot, your style declaration is just this:


indent {
margin-left:100px;
}

That would apply to ...

You could always import your old style sheet in before the new style sheet.

That way you'd get the newer styles defined later in the cascade so you'd get the new styles with your old customizations (that weren't overridden). Then, where there is a conflict (you don't see what you want), you go into ...

I'm not sure what you are asking. Do you mean in the bar where the search box and logo are? There isn't a way to do that by default, but I imagine you could find a jquery or similar script that would let you move the text of the first h1 up into the header area. That's not my area of expertise, but ...

Yes, but many bug reports make for faster fixes.

Barb,

Be sure to log a bug report on the CHM output issue as well so it makes it into MadCap's queue.

Flare 2016 and Flare 2017 variants all were contained in a "Flare 13" folder on your system, so you couldn't have multiple versions installed at the same time.

However, Flare 2018 is installed in a "Flare 14" folder on your system. This allows you to have Flare 2018 and a version of 2016-2017 on ...

Yes, best to contact MadCap in this case, and they can remotely invalidate the installation so you can "install" it again.

In the future, before you make changes to your AWS system, you will want to open Flare, and go to the Help ribbon. Click Deactivate Product. Then make any changes to your ...

Happy to have been able to help! In the forums, we love to help. Let us know if we can help in the future.

We have four authors that work in the same project. We use GIT for source control, but we don't bind our Flare project to GIT. We just use SmartGit as our source control tool outside of Flare.

It works really well for us. You do have to worry about merge conflicts occasionally, but as the four of ...

I don't know if the ::marker pseudo class is supported in PDF. There are *many* CSS3 features that are not fully supported by the engine that renders PDF output. I would contact MadCap Support and see if the ::marker pseduo class is supported or not.

Make sure that there aren't multiple body frames on your print page layout pages. I wonder if that was the root cause of this issue.

My bad. I missed that it was a PDF target. I also see the issue where when you build a PDF target, and click on the View Output button nothing happens. I'll submit this as a bug to MadCap. I suggest you do the same.

https://www.madcapsoftware.com/feedback/bugs/

Open the stylesheet in the text editor, and add the following to the bottom of the style sheet:
That should make it stay disappeared. At least it works in my sample project.

The decision probably hinges on whether you want to keep the child projects in sync with each other or not.

A template is taken at a single point in time. Projects based on the template inherit any template settings, but are not connected to the template anymore and any changes made need to be made ...

Clear your cache and clean your target to make sure there aren't any vestiges of the old settings in your output folders. I was able to switch a tri-pane output to the side nav without any issues, which doesn't help you much, I know.

If you have Analyzer (or Flare 2018, because these features are now built into Flare), you can find these references to undefined styles or undefined conditions, and remove them directly in Analyzer (or from the Flare Analysis tab in Flare 2018).

This looks to me like a style issue, so when you post the code from the topics, can you also post the styles used -- specifically the code for the styles that apply to the WallControl10 Server and the WallControl10 Client content.

1. When I add an image to the cover page (as per the instructions) when I build, the image appears on every single page in the document. When I just use text for the cover page its OK so obviously something is not right with how I am setting the image up. However, I can't fathom it out.

In your ...

It is working for me in my installation of 2018.

Be sure that you click on a build first, and make sure that the build you're trying to view completed. Obviously, if the build failed, then there is nothing to view.

That is ....... not intuitive. Thanks for posting what you found out. Sounds like a feature most people won't figure out on their own.

If the topic in the TOC is unlinked, then that isn't the place to be looking. I'd try looking at the very next topic, opening it in the editor and see if it has the "Chapter X" terminology. If so, it probably has a page-break-after enabled on that block, which puts that text on its own page.

I just tested it, and I see the same thing, even in the preview. I'd log a bug on this one.

https://www.madcapsoftware.com/feedback/bugs/