On Mon, Feb 7, 2011 at 9:17 PM, Mike Kaufman <mck...@gmail.com> wrote:
> On 2/7/11 9:28 PM, Eric Firing wrote:
>
> >>> Which backend are you using and using which OS?
> >>
> >> Good question. Snow Leopard and the MacOSX backend. If I use the Gtk
> >
> > This is a known bug in the MacOSX backend.
> >
> >> backend this bug does _not_ occur (though I have to use the plt.show()
> >> command to bring up the window --- which hangs the shell...)
> >
> > It should simply block until the window is closed; is this what you mean?
>
> Yes I do, although I'm not sure why it should block: I may want to add
> additional plots to the window --- though I do notice that if
> isinteractive=True, then the window doesn't block. It makes sense I
> guess, but not really intuitive, especially not coming from the
> behaviour of the OSX backend.
>
> M
>
>
The behavior in gtk and other backends is the designed/intended behavior.
macosx backend is actually the odd-man out because it was coded to only work
in one of those modes.
Maybe we should emit a warning when macosx backend is used when
interactive=False in order to dispel misunderstanding?
Ben Root
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
