Hi Gurus:
I'm having a serious problem with MultiCursor and autoscaling...
If I do the code below with both MultiCursor instantiations commented
out, then all plots are xscaled to [50,55] and yscaled to each plot's
appropriate ylimits.
If I uncomment the top MultiCursor instantiation, then b
I think there is: for a zoom/pan, the mouse must move a certain distance
to be considered the start of a zoom or pan (button down -> drag ->
button up). A pick can be just a click (button down -> button up, no or
minimal change in mouse position <1,2 pts?).
M
On 8/21/14 3:22 PM, Benjamin Root
Hmm, maybe my expectations are not common. Generally when I'm zooming in
on data, I want to zoom multiple times one right after another.
You always want this behavior when you're panning: you don't want the
pan tool to deselect after you release the button. I'm not quite sure
why anyone would w
since the mouse cursor looks totally
> different. I am curious why you would expect pick events to fire while
> using pan/zoom. What is the user-story that compels that expectation?
> Perhaps I could be convinced otherwise to offer some sort of toggle.
>
>
>
> On Thu, Aug 21, 2014
n Thu, Aug 21, 2014 at 12:01 PM, Thomas Caswell <mailto:tcasw...@gmail.com>> wrote:
>
> On Thu, Aug 21, 2014 at 9:44 AM, Michael Kaufman <mailto:kaufma...@ornl.gov>> wrote:
> >
> ># plot axvlines here... etc.
> >
>
Hi,
ipython 3.0.0-dev
matplotlib 1.3.1
GTKAgg backend
mac osx 10.9
If I create a pick_event on an axvline (with picker=6), there is no
problem triggering the pick event the first time the figure is shown (or
many times if I _don't_ zoom or pan). But if I then zoom in or pan
(using the toolbar