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
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
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 (
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
> >>...
> >>
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
--- 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
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
Best,
--Michiel.
--- On Sat, 11/13/10, John Hunter wrote:
> From: John Hunter
> Subject: Re: [Matplotlib-users] Mac OSX backend
> To: "Michiel de Hoon"
> Cc: "mdekauwe" , matplotlib-users@lists.sourceforge.net
> Date: Saturday, November 13, 2010, 9:22 AM
> On Sat,
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
t are there still
any such cases with the current organization of the drawing code in matplotlib?
Thanks,
--Michiel.
--- On Fri, 11/12/10, John Hunter wrote:
> From: John Hunter
> Subject: Re: [Matplotlib-users] Mac OSX backend
> To: "Michiel de Hoon"
> Cc: &q
On Thu, Nov 11, 2010 at 7:32 PM, Michiel de Hoon wrote:
> For this example, I am finding the exact same behavior with the Mac OS X
> backend as with the gtkcairo and gtkagg backends (on Mac OS X and Cygwin). If
> this is a bug, then which backend can we use as an example of the correct
> behavi
Hunter wrote:
> From: John Hunter
> Subject: Re: [Matplotlib-users] Mac OSX backend
> To: "mdekauwe"
> Cc: matplotlib-users@lists.sourceforge.net, "Michiel de Hoon"
>
> Date: Thursday, November 11, 2010, 7:39 AM
> On Thu, Nov 11, 2010 at 6:32 AM,
>
OK thanks so perhaps I should also try another backend then? What do other
mac users opt for?
ps. that works by the way.
John Hunter-4 wrote:
>
> On Thu, Nov 11, 2010 at 6:32 AM, mdekauwe wrote:
>>
>> It isn't any one script, if you did
>>
>> import numpy as np
>> import matplotlib.pyplot as
On Thu, Nov 11, 2010 at 6:32 AM, mdekauwe wrote:
>
> It isn't any one script, if you did
>
> import numpy as np
> import matplotlib.pyplot as plt
> x = np.arange(10)
> for i in xrange(10):
> plt.plot(x)
> plt.savefig('x.png')
>
> it pops up the plot window even though I didn't ask it to. I d
It isn't any one script, if you did
import numpy as np
import matplotlib.pyplot as plt
x = np.arange(10)
for i in xrange(10):
plt.plot(x)
plt.savefig('x.png')
it pops up the plot window even though I didn't ask it to. I don't get this
functionality on a non mac system. So I wonder if it
On Nov 11, 2010, at 4:15 AM, mdekauwe wrote:
>
> Hi,
> I have my backend set up in my .matplotlib/matplotlibrc file as:
>
> backend : MacOSX
>
> However if I run a script which does multiple plots and I don't ask the
> script to display the plots (i.e. not imshow()), I still get blank
Hi,
I have my backend set up in my .matplotlib/matplotlibrc file as:
backend : MacOSX
However if I run a script which does multiple plots and I don't ask the
script to display the plots (i.e. not imshow()), I still get blank windows
popping up. Does anyone else have this problem? Any soluti
17 matches
Mail list logo
