It is neither. At best it's a bug in the colorify filter. What
happens is this:
Each pixel has four components - three color components (red, green,
blue), and a transparency component (called alpha). An opaque pixel
has an alpha value of 1, a completely transparent one an alpha of 0.
Values in between give varying degrees of transparency.
Apparently what Gimp did when you deleted the background was to set
background pixel's alpha to 0. It didn't change the RGB values,
though. After all, if a pixel is fully transparent it doesn't matter
what its "color" is. So all the filter has to do is to take the RGB
values and use an alpha value of 1 to restore the image, like so:
filter magic (image in)
p = in(xy);
rgba:[p[0], p[1], p[2], 1]
end
The moral of the story is that filters should honor alpha values.
Here's a properly working colorify filter:
filter colorify (image in, gradient colors)
p = in(xy);
c = colors((gray(p)+t)%1);
rgba:[c[0], c[1], c[2], c[3] * p[3]]
end
I cannot reproduce the problem with the PNG file, though.
> ( colorfly seems buggy too,
> because instead
> then color convert to monochrome a colored image, but this is another
> issue)
I don't understand what you mean here.
Mark
No, it uses the colors from your current Gimp gradient to colorify the
image. The brightness of each pixel determines which color in the
gradient it will be mapped to.
Mark
So does that make it equivalent to Colours->Map->Gradient Map ?
-Rob A>
It seems it does.
Mark