MadCap Software Forums

I'm new to creating decent print layouts with actual front matter, etc. from Flare. As the title of the post suggests, I have a page-sized image (8.5" x 11"), and I've added it as a background to a page layout that is 8.5" x 11". The right side of the image has been cut off (perhaps the last half ...

That's true. Running out of drive space is one possible reason it wouldn't expand. And that's very easy to check

KevinDAmery wrote:Well, in theory Windows should never BSOD either....

Yes, but we hear about it frequently -- but I've *never* heard about the pagefile not auto-expanding when it was set to let Windows manage it.

Well I found a 'geek' to talk to and have been informed that I can whack my virtual memory paging size up to roughly 2.5 x the amount of RAM I have, so 10GB in my case. Apparently Windows is pretty rubbish at managing it's own page size - it only realises it's out when it really is out, not some ...

I'm curious: what is the date on the file specified as the problem? Was it from a previous build, or was it from the current build?

Something like that used to happen to me when I was editing very long topics that contained a lot of tables -- as I got near the end, things would get scrambled up with all kinds of strange lines (which looked like tables). Everything was fine in the sense that I could still edit, it just looked ...

It doesn't really bother me, since I only see it every so many days or weeks. However, an option to turn it off would be nice.

Have you ever checked on your current memory when this happens? You can do it quick 'n' dirty using Task Manager, or much more fine-grained using something like the performance monitor.

Have you tried this with the MadCap sample project?

Also, what target are you using (HTML Help, WebHelp, DotNet Help, PDF, etc.)?

I can generate HTML Help and WebHelp TOCs just fine from Flare 4.

Fixed -- I had the Patch Stylesheet and Image Links for HTML Help Printing checkbox enabled on my output. Disabled the checkbox, and I'm good.

I love MadCap support

I've never tried it, but I'd think it would be a very bad idea to use Flare 3.1 on projects along with Flare 4 -- Flare 4 makes certain changes to projects, and supports some things that Flare 3.1 does not. I would not be surprised if you ran into problems, and it would be very hard to troubleshoot ...

When I use Flare to resize images (using the click 'n drag corner), they do not show up in my HTML Help output; all I see is a small red X.

Is anyone else having this problem?

The simple workaround for this in my case is to never use Flare's internal text editor. I use Open WIth > Notepad (or Notepad++).

The problem I find with that is the if you do anything relating to hyperlinks the links end up pointing to a temp file instead of the proper topic. The internal text ...

You never installed DotNet 2.0 on your Vista box because Vista has 2.0 installed right out of the box.
No, .Net 3.0 is included with Vista. 2.0 is not.

Not so following the DotNet 2.0 installer. Run the dotnetfx.exe for DotNet 2.0 on Vista and you get this "error" message.
...which was my ...

You never installed DotNet 2.0 on your Vista box because Vista has 2.0 installed right out of the box.
No, .Net 3.0 is included with Vista. 2.0 is not.

I'm not entirely positive, but I think this is yes and no. Version 3.5 does contain the stuff from v1 and v2. However, Flare v3.1 was programmed ...

Well, I have no idea why it happened, but "index" referred to in the error has nothing to do with your documentation's index.

Rather, the error refers to the index for the collection (which is like an array if you are familiar with programming). The error is saying that the code tried to reference ...

The simple workaround for this in my case is to never use Flare's internal text editor. I use Open WIth > Notepad (or Notepad++).

My understanding is that every version since 2.0 was a superset of the previous version (1.x versions a different). So if you have 3.5 installed and 1.x installed, you are good. I know for a fact that I never installed .net 2.0 on my Vista box, and never had trouble with Flare, which targeted 2.0 ...

Leave Flare 4 open your desktop and leave your computer idle. Return an hour or so later the windows page file shrinks over time...

My recommendation to anyone who runs Windows (with or without Flare) is to use a static page file rather than letting Windows determine the size on its own. The ...

It was also a fairly major topic at the 2008 STC Summit.

DITA is "merely" another way to handle a lot of the things that Flare already does (with some additional capabilities above and beyond); it's an XML schema that describes structured, topic-based documents designed specifically for single ...

This is one of those features that probably should not have been called "Browse Sequence" in Flare, since it isn't what any former RoboHelp user would recognize as a browse sequence.

The only way to do this in Flare currently is to roll your own.

I pasted a few paragraphs from a PDF...no problems here.

Do the broken links also come up when you compile? I've noticed that if you try to overwrite one link with another, at times the one "underneath" doesn't entire go away, and shows up as a broken link.

LTinker68 wrote:Everyone's situation (and computer and working environment) is different. I've noticed some slowing, but it's not enough to affect my work.

Agreed -- on my fast computer, it isn't a problem. Slight slowing is not a major issue. For others, it might be different.

It's not typing that is slower; it was more cursor movement with the keyboard (for example, I often Ctrl-Tab around in a sentence or paragraph, and that was slightly slower -- this is after it was finished scanning).