Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Honouring the alpha attribute when creating composite images. #1955

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 13, 2013

Conversation

Westacular
Copy link
Contributor

I noticed some problems with the drawing of Images onto axes. Specifically, when option_image_nocomposite() is False and a single composite image is created (which seems to be the default for most backends), the alpha attribute of the Image objects was being ignored in the compositing process.

I've fixed that by multiplying the alpha component of each pixel with the attribute of the image, if set, during the process of compositing/blending the images together.

I've set up a test for this, as well, but getting the correct results from it depends on the changes from #1868.

In the process of testing this, I discovered that for output formats other than PNG, the Cairo backend was entirely failing to render images. I fixed that issue, however, a problem still remains: the Cairo image blending algorithms assume that pixel values are premultiplied by their alpha components, which is not currently being done in the process of converting image buffers for use by Cairo. For non-opaque images where rgb values exceed the alpha value, the result can be pretty weird and psychedelic. I can take a crack at fixing this, but it's a more involved change, and given that previously images weren't working at all for Cairo, it's perhaps better saved for a separate pull request.

@mdboom
Copy link
Member

mdboom commented Apr 29, 2013

👍 I agree we can save the Cairo fix for later. It looks as it the test images were perhaps not committed.

@Westacular
Copy link
Contributor Author

I've rebased/squashed this (with the formerly forgotten test images) and the Travis build is passing now.

@mdboom
Copy link
Member

mdboom commented May 6, 2013

👍

@@ -823,6 +825,16 @@
Image* thisim = static_cast<Image*>(tup[0].ptr());
ox = (long)Py::Int(tup[1]);
oy = (long)Py::Int(tup[2]);
if (tup[3].ptr() == Py_None)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure about this - does it not set an IndexError? (http://docs.python.org/2/c-api/tuple.html#PyTuple_GetItem)
I wonder if we'd be better checking the tuple's size?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I think I agree. To maintain backward compatibility, maybe do:

if (tup.size() <= 2 || tup[3].ptr() == Py_None)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. Everything that calls this in the codebase (all … 2 instances) was updated with the added parameter, but I'd forgotten the possibility that user code might call this.

pelson added a commit that referenced this pull request May 13, 2013
Honouring the alpha attribute when creating composite images.
@pelson pelson merged commit 3e9f4a6 into matplotlib:master May 13, 2013
@pelson
Copy link
Member

pelson commented May 13, 2013

Another fantastic piece of work @Westacular. Cheers!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants