MadCap Software Forums

Salvete omnes, I've been running Flare 2022 this week and it is noticeably slower than 2021R2, which I was running before. This is mostly affecting my largest project: there's often a considerable input delay when I'm typing in a topic, meaning I often have to pause and wait for the display to catch ...

It looks like when you're working in the Web medium the xrefs have a hyperlink style (blue with underline), even if that's not what's defined in the stylesheet. You must be working in the print medium - when I switch to print the hyperlink formatting disappears.

But either way, if you click on the ...

Thanks @Psider, that's a very neat trick!

Sorry to necro an old thread, but I'm going crazy over here... I've been trying to create screen tips with line breaks in them (not on an image map, just using the title attribute on an image). The funny thing is, on 2021 R2 I'm getting exactly the opposite behaviour from what bgilliland has ...

Ugh, this happened again even after I had fixed it >:(
Again, resolved by creating a new TOC and putting the same topics in it - but this time it took me a couple of attempts with different TOC names. This is extremely frustrating.

Ok, so your source files are stored on DevOps, and you publish the output files to the live Answer Centre. So in my mind the process looks like this (please correct me if I'm wrong here):

Source files in DevOps repository
--(Clone to PC)--> Source files on local PC
--(Make updates)--> Updated ...

I'm having a difficult time working out exactly what you mean here... What files are you "copying down" (pulling? downloading?) It sounds like you're pushing your *output* files to Devops to be built into the software, and you're also publishing output to a live answer centre - but why do you need ...

I don't think this should be a problem - we do a similar thing where we use the title of the first topic as our footer throughout the document, and it often includes variables with no problem. A couple of questions:

Is this just in the Flare UI, or is it a problem in the output as well?
What ...

You've listed good options, those are basically what I've come up with in the past when grappling with similar problems. Here are a few thoughts:

I think that branching is a good bet if you can get the processes right and everyone on the team understands what you're doing and why. It's a great ...

My colleague and I had the same problem for more than a year, and it was driving us mad. Especially because the last person in put team experienced no problems at all.
We were about to give up, when we started to compare the hardware on our computers. I turned out that the colleague that had no ...

As the list of linked topics is kept in the Analyzer database, deleting the Analyzer folder in the parent project (so it rebuilds) would probably fix it. I do this when I know the 'link viewer' list is incorrect.
Obviously I did that before trying anything else, thought that went without saying :P ...

Hmmm. Ok, the target thing seems to have been a red herring. What I'm finding is that the Auto-include linked files feature in the child project seems to base its understanding of the links on the Analyzer in the parent project (makes sense). When I looked at the TOCs in the parent project using the ...

Hmm, may have spoken too soon calling this one solved. I've tried the workaround recorded above and it seems to have worked *some* of the time. As in, some of the sub-TOCs have brought all of their topics through on import and others have not. Very frustrating!

Does anyone have any thoughts? I can ...

Salvete omnes, I've encountered an issue with the Flare project import function (global project linking) and am recording it here for posterity.

We generally keep all of our docs in a few large projects, but as part of my translation workflow I create a separate Flare project that only has one the ...

The print table of contents is based on the headings (h1, h2, etc) in the document, or more specifically the mc-heading-level style. For example, if you use an h1 in the topic, the mc-heading-level is 1 (by default), so it will appear at the top level of the print table of contents. (It's a little ...

Great solution everyone, I'll keep that one in mind for the future!

Could be worth watching the task manager when you're building your project or doing other taxing operations and see if Flare is sucking up large amounts of RAM or something - if your laptop has space for an upgrade that might improve the performance.

For comparison, I'm on Flare 2021 r2 and my ...

I'll also be adding to the beginning of each header that generates a separate .htm file according to some plan. In this case, it will be the module name. So I'll have moduleX-setup, moduleX-how to use, moduleX-troubleshooting, etc. This will generate unique image names as well!!! In Flare I'll have ...

I don't have super specific answers, but here's my advice:

I usually find it most convenient to import a document into a fresh project, then move it into the full project. That way you can do some basic cleaning up and organising with the new files without changing anything about your existing ...

Is there something more specific you're wondering about? Any single-sourcing setup is probably going to be highly personalised to the needs of your organisation, depending on what kinds of content you want to share and what outputs you're using.

The main thing that comes to mind for me is that ...

You could try Find & Replace and search for the text MadCap:conditions="*" with the following settings:

• Find in: Current Document
• Find in Source Code
• Search type: Wildcards

I think that should get you everything, and you can export from the find window if you need to!

When you create an import file, in the 'Include Files:' field put in the names of the targets you want to import. Check the 'Auto-include linked files' box. This should pull in just those targets and all of the files associated with them (TOCs, topics, stylesheets, etc.).

It looks like there's a new R3 version out - who's going to bite the bullet and try upgrading? If you do, report back on whether the problems are solved

Interesting to learn at least that Flare does handle files being stored in different projects!

Now that I read your initial post again, I wonder if you were running into problems because the Projects were stored in the Users folder on each PC? Those will have different paths because you are ...

I believe Flare is having trouble because it's not expecting files to be stored in different projects from the one you are publishing from. I would suggest restructuring your projects so that the files you need are always available in the same project. A couple of options:

Use Global Project ...