MadCap Software Forums

Let me also add, that if I do a checkout of the linked file while building Help, the status of the files becomes confused and I cannot check them in again when I'm done.

That is bug, I'm guessing.

Has anyone tried global linking with auto-include and using svn source control? It seems that if the linked files are checked in, Flare wants to check them out when I build because of the auo-include option.

The problem with this is if I've checked in everything and then see a small mistake and fix ...

I found a way to do this in Flare 7:

You need to install NetDrive so you can create a mapped drive to your WebDav location. Once that's done, you can create a destination in Flare to that location.

Then in the target:

Select the destination from the publishing tab.
Build the Help
Click the ...

Thanks for telling me about the attribute window. That's what I was looking for. I had forgotten about it.

For accessiblity purposes I need to include the scope attribute in table heads. I was hoping to include this in the table style or table editor but I don't seem to be able to.

Was this overlooked?

Thanks. That's a start. I'm guessing our project should take less than an hour to bind.

But somewhere between 64 MB and 250 MB the binding process breaks. If I can pin this down more, I"ll update this post.

We're having issues similar to this with a smaller (90) MB project. The writer involved waited 5 hours before stopping the initial binding effort.

Performance for large projects seems poor. Are there any numbers on this? How long should it take to bind a project that is 90 to 100 MB? An hour? More ...

In practical use, I find I still need TortoiseSVN because it provides commands that Flare does not.

That has more to do with our workflows than any deficiency on Flare's part.

Flare 7 does not seems to understand WebDAV at all. If I to point it to a webdav location, it says the file is missing. If I then give a validate HTTP url for a file, say the CSS, it still reports the file as missing even though the CSS is part of working project.

Clearly it is confused. Perhaps ...

I'd like to know what to expect before I upgrade. I've been tracking lots of issues in Flare 7 and the more of these that were addressed the better.

I've had this happen with Flare 7. I traced it down to the separator and the language skins. If I use a language other than US English and I include the separator in the webhelp toolbar none of the buttons appear.

The workaround is to create a custom button of my own with the same image on it. This ...

I opened the visio svg in illustrator and did not see the original image. This suggests that Visio does not write compatible svg.

I then took an illustrator file and saved it as svg. Flare had not problem with that file.

Note I saved the images as svg 1.1; don't know if that matters but I thought ...

And for clarification, I'm using Visio 2003. Don't know if a more recent version of Visio would have the issue.

But I can take the file and try to open it on my Mac to see if apps on that side have the same issue. Will report my results.

Yes I created the image in Visio.

I don't have another application to open the image; I thought of that so I can't tell if this is a Visio issue or not, hence the post.

I create create svg images with Visio and when I do this and insert the image in a topic, the arrowhead on my line disappears and the gradient shading on one image go solid gray.

Is that a flare problem or an svg issue?