> 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 differ
On 06/11/2010 10:02 PM, Michiel de Hoon 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 present s
--- On Sat, 6/12/10, Eric Firing 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 tkagg.
>
On 06/12/2010 05:37 AM, Michiel de Hoon wrote:
> --- On Sat, 6/12/10, Eric Firing 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;
So on Linux, show(block=True) blocks but show(block=False) doesn't? If
matplotlib is in interactive mode, does show(block=True) still block? Because
if matplotlib is in interactive mode, then the call to
matplotlib.interactive(True) shouldn't make a difference, and I would expect
show(block=Tru
