Re: [Matplotlib-users] Mac OSX backend

On Sat, Nov 13, 2010 at 7:58 PM, Michiel de Hoon wrote: > Thanks for your reply. > > Regarding your first question, how exactly does it disrupt your workflow? > Is it because the drawing takes too much time? Or because the focus switches > from the terminal window to the figure window? Or because

Re: [Matplotlib-users] Mac OSX backend

Thanks for your reply. Regarding your first question, how exactly does it disrupt your workflow? Is it because the drawing takes too much time? Or because the focus switches from the terminal window to the figure window? Or because the figure takes up screen space? Regarding the OP, my unders

Re: [Matplotlib-users] Mac OSX backend

Thanks for your reply. --- On Sat, 11/13/10, Eric Firing wrote: > In the gtk backend, draw_idle calls gobject.idle_add > > Thus, "idle" means the gui event loop has no higher > priority events.  Is > this condition reached only at the end of the script? With Python, there is only one thread (

Re: [Matplotlib-users] Mac OSX backend

On Sat, Nov 13, 2010 at 12:06 PM, Eric Firing wrote: > On 11/13/2010 06:16 AM, Michiel de Hoon wrote: > > --- On Sat, 11/13/10, John Hunter wrote: > >> Ie if we have a script like > >> > >># some plotting commands > >>... > >> > >># some expensive non GUI computation > >>... > >>

Re: [Matplotlib-users] Mac OSX backend

On 11/13/2010 06:16 AM, Michiel de Hoon wrote: > --- On Sat, 11/13/10, John Hunter wrote: >> Ie if we have a script like >> >># some plotting commands >>... >> >># some expensive non GUI computation >>... >> >># some update to plot above >>... >> >> Would we not run the ris

Re: [Matplotlib-users] Mac OSX backend

--- On Sat, 11/13/10, John Hunter wrote: > Ie if we have a script like > >   # some plotting commands >   ... > >   # some expensive non GUI computation >   ... > >   # some update to plot above >   ... > > Would we not run the risk that the GUI is idle in the non > GUI computation and therefo

Re: [Matplotlib-users] Mac OSX backend

On Sat, Nov 13, 2010 at 9:23 AM, Michiel de Hoon wrote: > Thanks for your reply. > But nowadays drawing is done through draw_idle, so we don't trigger > additional drawing even if interactive is True. In your example, if run as a > script, there is no drawing until a call to show() is made, rega

Re: [Matplotlib-users] Mac OSX backend

Thanks for your reply. But nowadays drawing is done through draw_idle, so we don't trigger additional drawing even if interactive is True. In your example, if run as a script, there is no drawing until a call to show() is made, regardless of whether interactive is True or False. Best, --Michiel

Re: [Matplotlib-users] Mac OSX backend

On Sat, Nov 13, 2010 at 7:46 AM, Michiel de Hoon wrote: > OK, thanks. With your example, I see a difference between the Mac OS X > backend and the TKAgg/GtkAgg backend but only if interactive is False in > matplotlibrc. If interactive is True, both the Mac OS X backend and the TkAgg > backend o

Re: [Matplotlib-users] Mac OSX backend

OK, thanks. With your example, I see a difference between the Mac OS X backend and the TKAgg/GtkAgg backend but only if interactive is False in matplotlibrc. If interactive is True, both the Mac OS X backend and the TkAgg backend open windows. Is this really the desired behavior? It seems counte

Re: [Matplotlib-users] Backgroundcolor for text

I wasn't able to replicate this bug with the MacOS backend. --Michiel On Sat Nov 13th, 2010 1:15 AM EST Jae-Joon Lee wrote: >I cannot reproduce this with agg, ps and pdf backend. >Maybe this bug is specific to the Mac oS X backend? > >Regards, > >-JJ > > >On Sat, Nov 13, 2010 at 5:19 AM, Bror J