RE: [Matplotlib-users] Re: [wxPython-users] Application Not Terminating

[<and...@ti...>]

Hello NGs,

>and...@ti... wrote:
>
>> On XP, I have Matplotlib 0.73 prerelease (that WAS a prerelease 1 mont=
hs
>> ago, nearly), while on Windows 2000 I have Matplotlib 0.74.
>> Well, I am using the WXAgg backend. By looking at backend_wx.py in 0.7=
3pre
>> (XP), I see that lines 116-117 are commented. These lines are:
>> 
>> # wxapp =3D wxPySimpleApp()
>> # wxapp.SetExitOnFrameDelete(True)
>> 
>Yes.  Having two app objects can certainly cause problems, although I 
>wouldn't have expected it to manifest this way.  Probably what is 
>happening is that when the spashscreen is closed it is being added to 
>the pending delete list but then the new app is being created and the 
>pending delete list is reinitialized and so the splash screen never gets=

>
>destroyed for real so the app's MainLoop keeps running waiting for it to=

>
>be destroyed.
>
>To find out for sure you could try uncommenting those lines on your XP

>box and see if you then have the same problem.
>

Ok Robin, I've done what you suggested: on my XP box I uncommented the 2
lines, and the application does NOT returns. So I found where the problem=

resides. It is not a wxPython nor a Windows issue, but a Matplotlib one.

Now I will probably leave them commented or I will add the Chris patch (c=
hecking
if a wx.App is already started or not). 
Finding this inconsistency in Matplotlib was a 2 weeks nightmare. 
Thanks for all your suggestions, NGs.

Andrea.