The most likely reason for this is that the files contain PNG files that are
24-bit. There's some kind of bug in Frame that inherits these color
definitions, but it doesn't seem to be hurtful, just messy. If you do have
PNGs in use, even if you clean up the definitions, they'll repopulate. To
fix this, all you need to do is resave the PNG in Photoshop or another
editor and knock the bit depth down to 8. You can also save them out as a
different file format, but then you'd have to change all the file names in
the FM docs, which is a large pain.
If you don't have PNGs, or after you fix them, you can prune the number of
color definitions down (although, again, they aren't hurting anything).
The slick/easy way to do this is with ITL's ReplaceColors FrameScript. It's
a freeby (http://www.itl.eu/108.0.html?&L=1), but you do need FrameScript
from Finite Matters (www.framescript.com) to run it.
Another way to do it is to use the CleanImport plug-in and specify a
template with only the colors you use.
art.campbell at gmail.com
"... In my opinion, there's nothing in this world beats a '52 Vincent and a
redheaded girl." -- Richard Thompson
No disclaimers apply.
On Thu, Jan 15, 2009 at 12:31 PM, Jack DeLand <jdeland1 at comcast.net> wrote:
> I have inherited some docs that have a huge number (dozens) of color
> definitions, all in RGB values. I want to edit these down to about 10
> entries that I actually need. Is there a fast and easy way to do this?
> Jack DeLand :: member, information architecture institute :: 734.629.7890
> :: www.jackdeland.com
> You are currently subscribed to Framers as art.campbell at gmail.com.
> Send list messages to framers at lists.frameusers.com.
> To unsubscribe send a blank email to
> framers-unsubscribe at lists.frameusers.com
> or visit
> Send administrative questions to listadmin at frameusers.com. Visit
> http://www.frameusers.com/ for more resources and info.