Location of Skin Image Files

This forum is for all Flare issues related to the HTML5, WebHelp, WebHelp Plus, and Adobe Air Targets
Post Reply
Cal Wilson
Propeller Head
Posts: 39
Joined: Wed Feb 22, 2006 8:33 am
Location: Conyers, GA

Location of Skin Image Files

Post by Cal Wilson »

I have a skin designed for HTML5.

I have defined a logo to be used for the skin in the HTMl5 Skin Editor, Styles, Logo, Background options.

In testing the results for the logo, I used several files until I obtained the desired results.

Now I have several image files that are associated with the skin (and it seems all projects).

I need to surgically remove some of the non-used all files.

Because I need to remove only specific files, the remove unreferenced images option is not viable.

Can someone tell me where the images associated with a skin are stored at the PROJECT level, not the output level?

I hope that it is possible to SIMPLY locate the image files in Windows Explorer and delete them.

Thank you for any assistance.
NorthEast
Master Propellus Maximus
Posts: 6426
Joined: Mon Mar 05, 2007 8:33 am

Re: Location of Skin Image Files

Post by NorthEast »

Images are embedded in the skin (*.flskn) file itself; there's no link/connection to the original file.

The Remove on save option will remove any unreferenced images from the skin file, i.e. images that you've previously added to the skin, but aren't currently using.

If you want some, but not all, of these unused images in the skin, I guess your options are:
- Use 'Remove on save', then add the (unused) images that you want in the skin.
- Back up the skin file, then edit the skin file in the text editor, and remove the appropriate <Resource> tag for the image.
Cal Wilson
Propeller Head
Posts: 39
Joined: Wed Feb 22, 2006 8:33 am
Location: Conyers, GA

Re: Location of Skin Image Files

Post by Cal Wilson »

@Dave Lee

Thanks for your suggestion.

I was able to change the skin file in an editor and remove the unwanted images.

However, I must say having to mess around in "code" like that in the editor is scary. Hopefully, a better approach will be developed for a future release.

Thanks again for helping me find another workaround.
Post Reply