When displaying an image with matshow, the values x,y of the cursor position is displayed. It would be useful to also display the value of the array at this position (tuple for RGB image with imshow).
I changed my mind about how hard it would be to write something bullet proof to make this work. The complication is that imshow (and iirc matshow is just imshow with the origin defaulting to the bottom instead of the top) takes both scalar data to be color mapped and RBG(A) data to just be displayed and can take the extent kwarg. All of the various permutations of those things would need to be dealt with gracefully.
One issue that @WeatherGod brought up in the other thread is that you can call imshow multiple times, presumably you want the cursor to show you the value for the 'correct' image as you mouse around the axes. To get that to work you now need each call to imshow to know about the existing images on the axes and update the call back. I think getting that right will be the biggest problem.
There is also a some-what related issue with re-doing how the call back stack works to display the (x,y) for stacked axes (see discussion at #2986 ).
Activity
tacaswell commented on Jun 24, 2014
Closing as a duplicate of #2477 .
tacaswell commented on Jun 24, 2014
Changed my mind, tagged for 1.5.x
PhML commented on Jun 24, 2014
Sorry for the duplicate, I didn't find it. But can you explain what changed your mind between January and now?
tacaswell commented on Jun 24, 2014
I changed my mind about how hard it would be to write something bullet proof to make this work. The complication is that imshow (and iirc matshow is just imshow with the origin defaulting to the bottom instead of the top) takes both scalar data to be color mapped and RBG(A) data to just be displayed and can take the extent kwarg. All of the various permutations of those things would need to be dealt with gracefully.
One issue that @WeatherGod brought up in the other thread is that you can call imshow multiple times, presumably you want the cursor to show you the value for the 'correct' image as you mouse around the axes. To get that to work you now need each call to imshow to know about the existing images on the axes and update the call back. I think getting that right will be the biggest problem.
There is also a some-what related issue with re-doing how the call back stack works to display the (x,y) for stacked axes (see discussion at #2986 ).
tacaswell commented on Jul 16, 2015
This has been taken care of by #3989