The improvements you list are long overdue. Thanks very much for taking this on. I hope you will also be able to fix the zooming and panning, so that it works in display space rather than in data space, but preserves the aspect ratio. In other words, it should be like using a magnifying glass to look at a map.

Where is zooming implemented? Obviously, it's not as simple as just settingcan_zoom to returnTrue. Is it just a special case instart/end_pan?

It's confusing because there are two kinds of zoom: the zoom box (zoom-to-rect), and the continuous zoom/pan. The latter is implemented in the PolarAxes.drag_pan() method, but for normal axes drag_pan and all the other zoom-to-rect and pan/zoom methods are in the backend_bases.py NavigationToolbar2. There are PRs in the works to refactor some of these things.@OceanWolf, can you provide some advice on how to proceed? Now I'm thinking that maybe at least for the zoom-to-rect functionality,@QuLogic should defer action until the refactoring is merged.

Ah, looking at that code, it makes sense that polar axes don't zoom quite right (if I enable it). Instead of applying some sort of cropped zoom, it just modifies the x/y limits, which in polar axes does not exactly produce a box, and of course wouldn't work before when you couldn't modify the limits at all... Though once I get the plot to actually crop to the wedge instead of leaving the full circle, maybe that won't be so bad.

Well, I'm finally getting there...

You can use the zoom button to zoom in, though it produces wedges instead of a rectangular crop. The pan/zoom button hasn't been changed yet.

There are a few hacks though, which I'll have to figure out eventually. Right now, in order to update the background patch, I've had to make thePolarAxes pretend it's a parent to the view/radial limits. Maybe there's a simpler way around that. Also, you'll notice that the background patch does not seem to be clipping the data. Is there some kind of update that I need to call?

Theta text 1 and text 2 are swapped now, so the tests are going to break. I'm not sure if I can switch them back or whether their visibility should just be swapped.

The transforms were hacked on until they worked, so I'm pretty sure they can be optimized slightly.

Don't have time to look at this right now, so very rough advice. New toolbar has been delayed until next release due to review delays, but as I don't think this will go in either for then, not a problem.

Basically in terms of zoom/panning, just take a look at the code in master inbackend_tools.py, that contains everything you need to know about the new toolbar. You can test it out onGtk3 and/orTkAgg by settingrcParam['toolbar'] = 'toolmanager'

@OceanWolf: FYI, that does not work:

File".../lib/matplotlib/pyplot.py",line518,infigure**kwargs)File".../lib/matplotlib/backends/backend_tkagg.py",line84,innew_figure_managerreturnnew_figure_manager_given_figure(num,figure)File".../lib/matplotlib/backends/backend_tkagg.py",line112,innew_figure_manager_given_figurefigManager=FigureManagerTkAgg(canvas,num,window)File".../lib/matplotlib/backends/backend_tkagg.py",line545,in__init__backend_tools.add_tools_to_manager(self.toolmanager)File".../lib/matplotlib/backend_tools.py",line971,inadd_tools_to_managertoolmanager.add_tool(name,tool)File".../lib/matplotlib/backend_managers.py",line221,inadd_tooltool_cls=self._get_cls_to_instantiate(tool)File".../lib/matplotlib/backend_managers.py",line307,in_get_cls_to_instantiateglobals(),locals(), [mod],-1)ValueError:levelmustbe>=0

Probably a Python 3 issue.

So this is nearly complete (WRT original goals) except for a couple issues:

• When I update the axes patch, none of the data lines/points/etc. are clipped! How do I get the other patches to re-clip themselves?
• The use of_invalidate_internal is a bit of a hack. It takes care of updating the axes patch dimensions, and the visibility of spines whenever any of the view parameters are changed. I was uncertain as to how theviewLim might be altered, so I found this to be the safest method. But if there is some sort of guarantee that it's only modified by method calls, I could make this more explicit.
• No matter what I return for the horizontal or vertical alignments of the radial tick labels on the first axis, they always seem to be in the same place! The second axis appears to work nicely.

I will try and tackle the pan/zoom and add some change documentation as well, but it would be helpful to get some insight on the above first.

I added some "what's new" text.

@efiring I can probably implement the modified zoom/pan, but the API between backend and axis is not very nice. The trouble is that the backend seems to think that the only relevant information is the view limit. That makes no sense on a polar axis if you want to use cartesian zoom. If I implement pan/zoom using an additional transform (for example), then the home/back/forth buttons will not work.

Maybe the thing to do is skip the Cartesian zoom/pan for the present PR, and enter it as a new wish-list issue. Then, if you are willing, you could attack it separately, making whatever larger changes are needed so that everything could work--presumably for other coordinate systems in addition to polar.@pelson, how have you handled zoom/pan in cartopy? Any ideas about this?

I am a bit concerned by the number of test images that have been changed.

Because theRadialLocator no longer limits ticks to positive values, the test results now include a tick at 0.0.

BTW, I should probably note that those image changes were ignored by the default threshold. The only reason I noticed is because one test image was wrong, and the difference was ignored until the added 0.0 triggered a failure.

Those zero-ticks don't look good; maybe they need to be special-cased away. I would consider them a regression.

I was debating that, but what should happen when you add an offset? Right now, you get a tick, but previously, you wouldn't.

@pelson, how have you handled zoom/pan in cartopy? Any ideas about this?

IIUC, Cartopy "cheats" by always plotting the projected space, which is in Cartesian coordinates.

On 2015/07/22 9:07 AM, Elliott Sales de Andrade wrote:

IIUC, Cartopy "cheats" by always plotting the projected space, which is
in Cartesian coordinates.

That's what Basemap does, but I thought Cartopy was using the mpl
transform machinery. Maybe not.

@mdboom, do you have any thoughts about this? The problem is that for non-affine projections like polar, we would like zoom and pan to work in Cartesian space. Zooming radially inward in a polar plot is rarely useful, if ever.

I should note that this issue is sort of similar to complaints about
mplot3d's "zooming" and "panning".

On Wed, Jul 22, 2015 at 3:27 PM, Eric Firingnotifications@github.com
wrote:

@mdboomhttps://github.com/mdboom, do you have any thoughts about this?
The problem is that for non-affine projections like polar, we would like
zoom and pan to work in Cartesian space. Zooming radially inward in a polar
plot is rarely useful, if ever.

—
Reply to this email directly or view it on GitHub
#4699 (comment)
.

@efiring OK, the central tick is now not shown if you are plotting a full non-annular circle. In the other cases, I feel there is no benefit to hiding it. It looks like there are enough minor changes for GitHub to still think most of the test images changed, but if you look at the actual diff, they haven't really. I will probably have to squash the change to make it happy (and I will anyway to avoid the extraneous binary diffs.)

I don't really understand why this is not passing on CI; it works fine locally and I made sure to use the correct local FreeType setting.

It took entirely too long to figure out that whenreset_ticks is called, I also needed to re-add the clip path on the ticks. Anyway, this seems to be back to working again.

@QuLogic Thank you for sticking with this. These are wonderful improvements.

Thanks!