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

pcolorfast results in invalid cursor data #6905

Closed
anntzer opened this issue Aug 5, 2016 · 2 comments · Fixed by #6930
Closed

pcolorfast results in invalid cursor data #6905

anntzer opened this issue Aug 5, 2016 · 2 comments · Fixed by #6930
Assignees
Milestone

Comments

@anntzer
Copy link
Contributor

anntzer commented Aug 5, 2016

mpl2.0b3 (and likely ever since get_cursor_data exists).
The PcolorImage class does not redefine the get_cursor_data method, so it displays incorrect cursor data:

In [1]: plt.gca().pcolorfast([0, 1, 3], [0, 2, 3], np.arange(4).reshape((2, 2)))

then hover the cursor over the image to see incorrect values in the status bar.

@jenshnielsen jenshnielsen added this to the 2.0.1 (next bug fix release) milestone Aug 7, 2016
@efiring efiring self-assigned this Aug 9, 2016
@anntzer
Copy link
Contributor Author

anntzer commented Aug 9, 2016

By the way, the NonUniformImage class suffers from the same problem. This is less obvious from the example (pylab_examples/image_nonuniform.py) as it directly adds the image to ax.image, so the image is not added to the mouseover set. But switching these lines to use ax.add_image(im) reveals the same issue.

@efiring
Copy link
Member

efiring commented Aug 9, 2016

Yes, I'm aware of that, but it is lower priority because as far as I know we have no direct Axes interface like pcolorfast to the NonUniformImage class; I suspect it is rarely if ever used. (I don't know how much use pcolorfast gets, for that matter; I wrote it because I wanted it, and I use it, but maybe no one else does.) Also, handling the data cursor for PcolorImage is fast and easy. It's not so obvious to me how to handle NonUniformImage.

@QuLogic QuLogic modified the milestones: 2.0 (style change major release), 2.0.1 (next bug fix release) Aug 25, 2016
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 a pull request may close this issue.

5 participants