I'm using an external library that generates a BGR32 image. The source image is only 24bpp, so the alpha channel is all zeroed. So, when I add the image to an evas canvas and use evas_object_image_data_set, I pass 0 to evas_object_image_alpha_set. My assumption is that this merely indicates to Evas that the alpha bytes aren't meaningful. But in practice, it means that if I pass an alpha value less than 255 to evas_object_color_set, the image goes away.
Clearly the alpha from the image is getting multiplied. But since has_alpha = false, I think this behavior is a bug. But before I took the time to see about fixing it and submitting a patch, I thought I'd verify here that such a patch would be accepted. Cheers, Jason.
signature.asc
Description: This is a digitally signed message part
