Skip to content
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

macosx backend broken by #901: QuadMesh fails so colorbar fails #996

Closed
efiring opened this issue Jul 10, 2012 · 6 comments
Closed

macosx backend broken by #901: QuadMesh fails so colorbar fails #996

efiring opened this issue Jul 10, 2012 · 6 comments

Comments

@efiring
Copy link
Member

efiring commented Jul 10, 2012

backend_macosx.py and _macosx.m need to be updated to handle the QuadMesh change in which edgecolors are passed in place of showedges. As it is, it fails with an exception. This is illustrated by any attempt to make a colorbar, for example.

@oxling
Copy link
Contributor

oxling commented Jul 10, 2012

We fixed the issue causing the exception by updating _macosx.m to expect a PyObject * instead of an int. See commits 02f8a65 and 3c7b5ee.

However, the colorbar is still drawn blank. Does anyone have any tips as to where the colobar drawing code should be for the OSX renderer? I'd like to fix the whole issue before submitting a pull request.

@efiring
Copy link
Member Author

efiring commented Jul 10, 2012

On 2012/07/10 9:25 AM, Amy wrote:

We fixed the issue causing the exception by updating _macosx.m to expect a PyObject * instead of an int. (See commits 02f8a65 and 3c7b5ee.)

It requires much more than that; Michiel de Hoon, the macosx maintainer,
is going to take care of it shortly.

However, the colorbar is still drawn blank. Does anyone have any tips as to where the colobar drawing code should be for the OSX renderer? I'd like to fix the whole issue before submitting a pull request.

The problem is not with the colorbar code, it is a matter of fixing
macosx correctly, so please just wait for Michiel's work.


Reply to this email directly or view it on GitHub:
#996 (comment)

@mdehoon
Copy link
Contributor

mdehoon commented Jul 15, 2012

See Pull Request #1011

efiring added a commit that referenced this issue Jul 15, 2012
@efiring
Copy link
Member Author

efiring commented Jul 15, 2012

On 2012/07/15 3:22 AM, mdehoon wrote:

See Pull Request #1011


Reply to this email directly or view it on GitHub:
#996 (comment)

Thank you! It works for me, so I committed it; I did not see any reason
to wait for more review, since we don't seem to have many people looking
at this code.

I started a new issue, however, because both before and after this
change, compilation yields warnings. Maybe not a big deal, but it is
nicer to see a perfectly clean compilation.

#1013

Eric

@mdehoon
Copy link
Contributor

mdehoon commented Jul 16, 2012

Hi Eric,
These compilation warnings only occur with Mac OS X 10.6 or later. I can look at this later this week when I get access to a mac with a recent OS.
-Michiel


On Sun, Jul 15, 2012 3:39 PM EDT Eric Firing wrote:

On 2012/07/15 3:22 AM, mdehoon wrote:

See Pull Request #1011


Reply to this email directly or view it on GitHub:
#996 (comment)

Thank you! It works for me, so I committed it; I did not see any reason
to wait for more review, since we don't seem to have many people looking
at this code.

I started a new issue, however, because both before and after this
change, compilation yields warnings. Maybe not a big deal, but it is
nicer to see a perfectly clean compilation.

#1013

Eric


Reply to this email directly or view it on GitHub:
#996 (comment)

@WeatherGod
Copy link
Member

Should this issue be closed?

@efiring efiring closed this as completed Jul 17, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants