Hm. Have upgraded to 0.71. Now I don't get the error message
> anymore, however, once I close the figure window, the IDLE
> (-n) prompt doesn't respond anymore. (Same scenario as
> described in last email.)
> Ideas?
Well, if you are using matplotlib interactively from within IDLE< then
interactive : True should be set in your rc file, no?
JDH
John,
> Hm. Have upgraded to 0.71. Now I don't get the error message
> anymore, however, once I close the figure window, the IDLE
> (-n) prompt doesn't respond anymore. (Same scenario as
> described in last email.)> Ideas?
Well, if you are using matplotlib interactively from within IDLE< then
interactive : True should be set in your rc file, no?
I didn't make myself very clear, or I have misunderstood the meaning of "interactive". I presumed that 'interactive' means: I issue the plot command and the figure pops up immediatly, etc.
Not interactive (in my understanding) means that I issue all the matplotlib commands I'd like to use and at the end I can use show() to display the picture.
I presumed that when I close the figure windows (by clicking on the right symbol on the window), I could carry on using the IDLE session (in this example).
Here is the bit that I didn't expect and assumed would be some kind of bug:
I need to kill IDLE (when clicking on the symbol in the upper right hand corner of the IDLE -n window in MS XP, I get the message :" The program is still running! Do you want to kill it?"). In summary, I can't carry on using the session once I have used the show() command.
Thanks,
Hans