John, you added this logic with comment, "added support
> for multiple overlapping axes with pan/zoom". I think
This was a user contributed patch, but I did check it in.
> for a user to address this problem correctly they should
> use the zorder property. I added a check a while back
> that sets the inaxes property of a LocationEvent to the
> highest zorder if multiple axes are found.
It's a little more than zorder, though, since in the case of
examples/two_scales.py you have to axes that entirely overlap one
another, and you may want both to respond to navigation. In general I
like the idea of using zorder to determine which axes responds to
navigation commands, but do you think it can handle this case as well.
> Fixed in svn.
Thanks for looking into this one.