Re: [matplotlib-devel] repeated calls to show() are now OK?

2010-06-13 Thread Michiel de Hoon
=True) and show(block=False) to behave the same way. --Michiel. --- On Sat, 6/12/10, Eric Firing efir...@hawaii.edu wrote: From: Eric Firing efir...@hawaii.edu Subject: Re: [matplotlib-devel] repeated calls to show() are now OK? To: Michiel de Hoon mjldeh...@yahoo.com Cc: John Hunter jdh2

Re: [matplotlib-devel] repeated calls to show() are now OK?

2010-06-13 Thread Eric Firing
on the first call, so I did not realize that the tkagg behavior was identical on linux and mac, as one would expect. Eric --Michiel. --- On Sat, 6/12/10, Eric Firingefir...@hawaii.edu wrote: From: Eric Firingefir...@hawaii.edu Subject: Re: [matplotlib-devel] repeated calls to show

Re: [matplotlib-devel] repeated calls to show() are now OK?

2010-06-13 Thread Michiel de Hoon
--- On Fri, 6/11/10, Eric Firing efir...@hawaii.edu wrote: I agree that the difference in blocking behavior is still a problem. I think that what we should do for now, *if* multiple calls to show work on the Mac (which I can't easily test), is change the documentation to correspond to the

Re: [matplotlib-devel] repeated calls to show() are now OK?

2010-06-13 Thread Daniel Welling
Something that I have noticed: When using TkAgg (python 2.5, OSX/ppc, mpl 99.0), isinteractive() switches from False to True after the first call to show() (see below). When I switch back ends, e.g. to Qt4, this change does not happen until I do it myself through ion(). This was reproduceable on

Re: [matplotlib-devel] repeated calls to show() are now OK?

2010-06-13 Thread Eric Firing
On 06/13/2010 07:39 AM, Daniel Welling wrote: Something that I have noticed: When using TkAgg (python 2.5, OSX/ppc, mpl 99.0), isinteractive() switches from False to True after the first call to show() (see below). When I switch back ends, e.g. to Qt4, this change does not happen until I do

Re: [matplotlib-devel] repeated calls to show() are now OK?

2010-06-12 Thread Michiel de Hoon
I agree that the difference in blocking behavior is still a problem. I think that what we should do for now, *if* multiple calls to show work on the Mac (which I can't easily test), is change the documentation to correspond to the present situation, highlighting the real problem of different

Re: [matplotlib-devel] repeated calls to show() are now OK?

2010-06-12 Thread Michiel de Hoon
--- On Sat, 6/12/10, Eric Firing efir...@hawaii.edu wrote: With TkAgg on Mac OS X, the first call to show() blocks, and returns when all figures are closed by the user. However, subsequent calls to show() return immediately. This is anomalous, then; on linux, no call to show blocks with

Re: [matplotlib-devel] repeated calls to show() are now OK?

2010-06-12 Thread Eric Firing
On 06/12/2010 05:37 AM, Michiel de Hoon wrote: --- On Sat, 6/12/10, Eric Firingefir...@hawaii.edu wrote: With TkAgg on Mac OS X, the first call to show() blocks, and returns when all figures are closed by the user. However, subsequent calls to show() return immediately. This is anomalous,

[matplotlib-devel] repeated calls to show() are now OK?

2010-06-11 Thread Eric Firing
It seems that every couple of weeks, someone understandably asks why one can't call show() more than once in a script or session. However, I think that at least on all non-Mac backends, it now works. I have tested it (using ipython, with no threading) on: qtagg, qt4agg, wx, wxagg, gtk,

Re: [matplotlib-devel] repeated calls to show() are now OK?

2010-06-11 Thread John Hunter
On Fri, Jun 11, 2010 at 2:56 PM, Eric Firing efir...@hawaii.edu wrote: Is it time for us to change our documentation, and officially support the use of multiple calls to show()?  If we can do it, I think it would remove one of the main stumbling blocks for newcomers. I don't have a problem

Re: [matplotlib-devel] repeated calls to show() are now OK?

2010-06-11 Thread Eric Firing
On 06/11/2010 10:09 AM, John Hunter wrote: On Fri, Jun 11, 2010 at 2:56 PM, Eric Firingefir...@hawaii.edu wrote: Is it time for us to change our documentation, and officially support the use of multiple calls to show()? If we can do it, I think it would remove one of the main stumbling