Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

%matplotlib notebook and procedural interface #4453

Closed
tritemio opened this issue May 21, 2015 · 4 comments
Closed

%matplotlib notebook and procedural interface #4453

tritemio opened this issue May 21, 2015 · 4 comments

Comments

@tritemio
Copy link

When using %matplotlib notebook with the procedural interface, figures are not closed when the red 'x' button is pressed (the figure becomes static, but the figure object is not closed).

After closing the figure by clicking on the red 'x' button, no other plot is displayed until close() is called. Is this a deliberate choice? I think it may be confusing for newbies.

DISCLAIMER: I know that the OO interface is preferred. However, the procedural interface has its use-case for a first-time users (plus allows saving some typing).

@tritemio tritemio changed the title %matplolib notebook and procedural interface %matplotlib notebook and procedural interface May 21, 2015
@WeatherGod
Copy link
Member

Which version of matplotlib and ipython are you using? I think this is a
bug that was recently fixed in master.

On Thu, May 21, 2015 at 2:46 PM, Antonino Ingargiola <
notifications@github.com> wrote:

When using %matplotlib notebook with the procedural interface, figures
are not closed when the red 'x' button is pressed (the figure becomes
static, but the figure object is not closed).

After closing the figure by clicking on the red 'x' button, no other plot
is displayed until close() is called. Is this a deliberate choice? I
think it may be confusing for newbies.

DISCLAIMER: I know that the OO interface is preferred. However, the
procedural interface has its use-case for a first-time users (plus allows
saving some typing).


Reply to this email directly or view it on GitHub
#4453.

@tritemio
Copy link
Author

Great to know it has been fixed!

I'm using matplotlib 1.4.3 with python 3.4 under Anaconda for windows 7 x64.

Is this a bug in all the platforms? Is there a workaround until the next release?

@tritemio
Copy link
Author

I forgot to mention the ipython version is 3.1.

@tritemio
Copy link
Author

@WeatherGod, I found the previous issue, unfortunately is still open: #4281.

I think we can close this as duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants