Mising Skin Images in Webhelp Output

[Alicia143]

I sent in new help files to our developers recently. They are complaining about errors in the background processing due to missing image files for the skin. The webhelp appears perfectly on the servers, but there are errors in the background. When I checked these images files, I saw that none of them are used for the current skin, but there is code that still wants them there. I told the developer to fix the GUI code that it wasn't an issue with Flare; however, I am not sure that is true.

This is what he told me....
The missing files are still needed. They are referenced from javascript code of the WebHelp support library. For Example:
File: /Content/SkinSupport/MadCapAll.js
Contains the following code: MakeButton(td,"Back","Images/Back.gif","Images/Back_over.gif","Images/

Can anyone tell me why the skin needs buttons that I don't use? I know these are the standard Flare buttons for the skin, but we have our own. If I do need these unused image files in the Webhelp>Skin>Images folder, then why are they not automatically compiled now when they appear to have been compiled when I sent the help in a few months ago? Any ideas?

[NorthEast]

Can anyone tell me why the skin needs buttons that I don't use? I know these are the standard Flare buttons for the skin, but we have our own. If I do need these unused image files in the Webhelp>Skin>Images folder, then why are they not automatically compiled now when they appear to have been compiled when I sent the help in a few months ago? Any ideas?

I don't know why the js file refers to unused images (that's a question for MadCap), but I would guess that the difference in builds might be caused by the Generate all skins setting in the target's Advanced tab. If this setting is off, it will generate skin files only for the skin selected in the target; if it is on, it will create skin files for all the skins in the project. You'd enable this setting if you want to use multiple skins, e.g. specify different skins in CSH calls.

[i-tietz]

I don't know why the js file refers to unused images (that's a question for MadCap), but I would guess that the difference in builds might be caused by the Generate all skins setting in the target's Advanced tab. If this setting is off, it will generate skin files only for the skin selected in the target; if it is on, it will create skin files for all the skins in the project. You'd enable this setting if you want to use multiple skins, e.g. specify different skins in CSH calls.

I think it's a matter of performance. Otherwise Flare would have to find out (during build) what pics are used.
It's not Generate all skins because we have that turned off and still have "spare" pics ...

[NorthEast]

I don't know why the js file refers to unused images (that's a question for MadCap), but I would guess that the difference in builds might be caused by the Generate all skins setting in the target's Advanced tab. If this setting is off, it will generate skin files only for the skin selected in the target; if it is on, it will create skin files for all the skins in the project. You'd enable this setting if you want to use multiple skins, e.g. specify different skins in CSH calls.

I think it's a matter of performance. Otherwise Flare would have to find out (during build) what pics are used.
It's not Generate all skins because we have that turned off and still have "spare" :wink: pics ...

The Generate all skins option would explain why two builds may include different sets of skin images; i.e. you would have a folder of images for each skin in Data/SkinName.

The generated skin images will still include unused files; Flare automatically includes a set of standard images, and it also includes any image that you have imported into the skin, regardless of whether or not it is used.