butt...@gmail.com, 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 int
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, wrote:
> Hi,
>
> Does matplotlib keep track of the last object
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 Fals
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
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
On Mon, Apr 4, 2011 at 5:57 PM, Eric Firing 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 wit
On 04/04/2011 12:35 PM, Darren Dale wrote:
> On Mon, Apr 4, 2011 at 5:57 PM, Eric Firing 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
Tried the fix over a 1.0.0 installation a few months old and it works, but
there are issues with blocking, which I have encountered before.
I will try on the current snapshot, and also adapt your fix to a 0.99
release which has a blocking behaviour that I understand better.
efiring wrote:
>
>
