Flare4 large chm files

[booey]

Going from Flare 3.1 to 4 I notice that the compiled chm is now about 80% bigger than the 3.1 compiled chm. Anyone else find this?

[Richard Ferrell]

If you have this issue you may want to open a support ticket

https://www.madcapsoftware.com/support/contact.aspx

[booey]

Looking further into this i find the extra size is due to the second image file that Flare creates when the "Generated resized copies of scaled images" option is set in the Advanced tab of the target. Why the default setting for this is on defies my understanding. It has caused almost as much waste of time for us as having the "Add DOCTYPE declaration to generated topics', also a new option in advanced target settings, set on by default. Surely Madcap must know that if you introduce optional functionality in a new release you have the default setting so that the new version operates as the previous version did. It is then up to the user to choose to take advantage of the functionality, not have it pushed down their throats without warning. Backwardly compatable means more than "an existing project will work in a new version" it means "an existing project will work IN EXACTLY THE SAME WAY in a new version". Unless under the hood changes make it impossible in which case the user is clearly warned.

Having spent hours going through 38 projects to uncheck the "add DOCTYPE" check box we now have to go through them all again to uncheck the "resized images' check box. This is in addition to all the other fiddly little things that Flare has covertly changed in the way it functions that we have had to accomodate. And no it doesnt work if you just use a grep and add the "false' statement to the .fltar file, I tried that already.

[Bea Lac]

Hello,
I am in the same case : I went from Flare 3.1 to 4 and the chm files are very bigger (x3 or x10 depending on the project).
I suspect the new function "Global Project Linking—Importing Files from Other Projects".
I have created a Sharing project with all images, snippets, variables and destinations.
Each child project imports all files from the Sharing project.
It is very convenient to use but I can not provide such heavy chm files !!!

Is there anywhere an option to remove the unused elements from the chm target ?

Nota: regarding the "resized images" check box, I already unchecked it in all my projects.