On 01/09/06, Eric Firing <efiring@...> wrote:
> Scott,
>
> This is fixed now in svn. (I will probably go back shortly and make
> another change to improve efficiency.) There was a one-line bug in
> contour.py, but the fundamental problem was that colors.ColorConverter
> (which handles color inputs for collections, among other things) was
> stripping off the alpha value and replacing it with 1.0.
Eric,
Now that this bug is sorted, will it enable pcolormesh to use alpha =
0 to not plot missing data?
--George.

George Nurser wrote:
> On 01/09/06, Eric Firing <efiring@...> wrote:
>> Scott,
>>
>> This is fixed now in svn. (I will probably go back shortly and make
>> another change to improve efficiency.) There was a one-line bug in
>> contour.py, but the fundamental problem was that colors.ColorConverter
>> (which handles color inputs for collections, among other things) was
>> stripping off the alpha value and replacing it with 1.0.
>
> Eric,
> Now that this bug is sorted, will it enable pcolormesh to use alpha =
> 0 to not plot missing data?
George,
Unfortunately not--it is a completely different bug. A while ago I
tracked the pcolormesh alpha bug down into the bowels of the quadmesh
code, where it is making fairly low-level Agg calls. I didn't write
quadmesh, I have never dealt with Agg directly, and I don't think I can
afford the time that it would take for me to understand it--assuming I
could. So, I've been unable to fix the pcolormesh alpha bug. I think
it will require an Agg wizard, preferably one of the original quadmesh
authors.
Eric