matplotlib-devel Mailing List for matplotlib

On 04/04/2011 12:35 PM, Darren Dale wrote:
> On Mon, Apr 4, 2011 at 5:57 PM, Eric Firing<ef...@ha...> wrote:
>> On 04/04/2011 10:24 AM, Darren Dale wrote:
>>> When I run some of the examples in pylab_examples, like
>>> simple_plot.py, the call to show() yields a window that immediately
>>> closes. This is with either the v1.0.x or master branches on OS X with
>>> python 2.7 and the qt4 backend, with interactive=True in matplotlibrc.
>>> When I change interactive to False, the window remains open until I
>>> close it.
>>>
>>> Is interactive=True not supported for scripts anymore?
>>
>> After testing and thinking a bit, I think the answer is that it never
>> was, unless you are in an environment like ipython. Certainly it hasn't
>> been any time recently. A script run from the command line exits when
>> it reaches the last line; if nothing blocks, then it will immediately
>> close the window and exit. This is not backend-dependent or
>> OS-dependent--it is just the way scripts work.
>
> I thought I remembered there being two separate issues: whether or not
> to block, and whether a plot is updated after each command or
> rendering is deferred until show() is called. Things may have changed
> when IPython pulled the threading monkeypatches, more likely my memory
> is bad. Your explanation makes sense. Thanks.
>
> Darren
Darren,
You are correct that interactive mode does have two effects, and I was 
only describing one--whether show blocks. The other effect of 
interactive mode is that pyplot commands, which include 
draw_if_interactive() calls, draw immediately when in interactive mode 
but draw only upon execution of show() when in non-interactive mode.
Eric

On Mon, Apr 4, 2011 at 5:57 PM, Eric Firing <ef...@ha...> wrote:
> On 04/04/2011 10:24 AM, Darren Dale wrote:
>> When I run some of the examples in pylab_examples, like
>> simple_plot.py, the call to show() yields a window that immediately
>> closes. This is with either the v1.0.x or master branches on OS X with
>> python 2.7 and the qt4 backend, with interactive=True in matplotlibrc.
>> When I change interactive to False, the window remains open until I
>> close it.
>>
>> Is interactive=True not supported for scripts anymore?
>
> After testing and thinking a bit, I think the answer is that it never
> was, unless you are in an environment like ipython. Certainly it hasn't
> been any time recently. A script run from the command line exits when
> it reaches the last line; if nothing blocks, then it will immediately
> close the window and exit. This is not backend-dependent or
> OS-dependent--it is just the way scripts work.
I thought I remembered there being two separate issues: whether or not
to block, and whether a plot is updated after each command or
rendering is deferred until show() is called. Things may have changed
when IPython pulled the threading monkeypatches, more likely my memory
is bad. Your explanation makes sense. Thanks.
Darren

On 04/04/2011 10:24 AM, Darren Dale wrote:
> When I run some of the examples in pylab_examples, like
> simple_plot.py, the call to show() yields a window that immediately
> closes. This is with either the v1.0.x or master branches on OS X with
> python 2.7 and the qt4 backend, with interactive=True in matplotlibrc.
> When I change interactive to False, the window remains open until I
> close it.
>
> Is interactive=True not supported for scripts anymore?
After testing and thinking a bit, I think the answer is that it never 
was, unless you are in an environment like ipython. Certainly it hasn't 
been any time recently. A script run from the command line exits when 
it reaches the last line; if nothing blocks, then it will immediately 
close the window and exit. This is not backend-dependent or 
OS-dependent--it is just the way scripts work.
Eric

On 04/04/2011 10:24 AM, Darren Dale wrote:
> When I run some of the examples in pylab_examples, like
> simple_plot.py, the call to show() yields a window that immediately
> closes. This is with either the v1.0.x or master branches on OS X with
> python 2.7 and the qt4 backend, with interactive=True in matplotlibrc.
> When I change interactive to False, the window remains open until I
> close it.
>
> Is interactive=True not supported for scripts anymore?
No, everything is supposed to work with both values of interactive. The 
difference is supposed to be that show blocks only in non-interactive mode.
I see the same problem with qt4agg backend on linux. I don't think it 
was doing that back when I was working on show, so I suspect something 
changed in qt4agg backend; either that, or this is something I thought I 
tested but didn't. It still works under ipython from git.
Eric

When I run some of the examples in pylab_examples, like
simple_plot.py, the call to show() yields a window that immediately
closes. This is with either the v1.0.x or master branches on OS X with
python 2.7 and the qt4 backend, with interactive=True in matplotlibrc.
When I change interactive to False, the window remains open until I
close it.
Is interactive=True not supported for scripts anymore?

Sorry, my question was not clear.
What you mention works, IF you know the last plotted object was a line
and not a text...
My question relates to trying to find this type of information automatically.
On Mon, Apr 4, 2011 at 7:15 AM, <bu...@gm...> wrote:
> Hi,
>
> Does matplotlib keep track of the last object added to the plot axes or its
> nature (line, text, collection, patch, etc.) ?
> If not, would it be feasible to implement something like this in matplotlib
> ?
>
> This could be useful for interactive plotting, as it would allow a simple
> undo feature based on commands such as del ax.lines[-1].
-- 
thanks,
peter butterworth

bu...@gm..., on 2011年04月04日 05:15, wrote:
> Hi,
> 
> Does matplotlib keep track of the last object added to the plot axes
> or its nature (line, text, collection, patch, etc.) ?
> If not, would it be feasible to implement something like this in
> matplotlib ?
> 
> This could be useful for interactive plotting, as it would allow a
> simple undo feature based on commands such as del ax.lines[-1].
Hi there,
I think this functionality already exists exactly as you
describe. ax.plot appends new lines to ax.lines, ax.scatter
appends new collection to ax.collections (via the
ax.add_collection method).
try this, and you'll see the cyan line is removed:
plt.plot([1,2,3],'r')
plt.plot([1,2,1],'c')
ax = plt.gca()
del(ax.lines[-1])
plt.draw()
-- 
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7 

Hi,
Does matplotlib keep track of the last object added to the plot axes or its 
nature (line, text, collection, patch, etc.) ?
If not, would it be feasible to implement something like this in 
matplotlib ?
This could be useful for interactive plotting, as it would allow a simple 
undo feature based on commands such as del ax.lines[-1].

On 04/02/2011 02:48 PM, bdb112 wrote:
>
> Cannot pick markers '+','x' or others with zero area in plots made by
> pyplot.scatter
>
> The example below
> http://old.nabble.com/file/p31305303/picker_example_scatter.py
> picker_example_scatter.py is from the matplotlib docs, but modified to use
> scatter instead of plot (which works fine).
> http://matplotlib.sourceforge.net/users/event_handling.html#picking-exercise
>
> run picker_example_scatter.py
> <will not respond to any picks>
> edit code replace 'x' with 'o'
> <Works, but only if click is inside marker - i.e. ignores picker value.>
>
> See also
> http://old.nabble.com/Can't-pick-on-various-scatter-markers-tp19140977p19140977.html
> which describes the same problem.
>
> Ububtu 10.04 LTS
> matplotlib 0.99.1.1
> Python 2.6.5 (r265:79063, Apr 16 2010, 13:09:56)
>
>
See https://github.com/matplotlib/matplotlib/pull/72 for a possible 
solution.
Eric