2.1. How it works
IconHacks also will automatically select an icon shape for newly created (or edited or saved) files, based on the extension of the file, and whether the viewer is considered to be edited or not. The icons to be used must have been registered with IconRegistry. The icon to be used will be the first of the following:
1) The icon specified by the profile entry "IconHacks.Icon.extension". (It will also check for "IconHacks.DirtyIcon.extension" first if the viewer is edited.)
2) If the icon "extension" is registered (and "Dirtyextension" if ...), then it will use that one.
3) The icon specified by the profile entry "IconHacks.DefaultIcon". (It will also check for "IconHacks.DirtyDefaultIcon" first if the viewer is edited.)
4) Whatever the client code which created the viewer requested.
The following profile entry may by added to your profile to get one such mapping. (N.B. If you use Remember or another package which uses IconRegistry, you may need to fold these in as additions.)
RegisteredIcons: "
Mesa: ///7.0/Commands/IconHacks.Icons 0
DirtyMesa: ///7.0/Commands/IconHacks.Icons 1
Tioga: ///7.0/Commands/IconHacks.Icons 2
DirtyTioga: ///7.0/Commands/IconHacks.Icons 3
Df: ///7.0/Commands/IconHacks.Icons 4
DirtyDf: ///7.0/Commands/IconHacks.Icons 5
Config: ///7.0/Commands/IconHacks.Icons 6
DirtyConfig: ///7.0/Commands/IconHacks.Icons 7
Errlog: ///7.0/Commands/IconHacks.Icons 8
DirtyErrlog: ///7.0/Commands/IconHacks.Icons 9
"