Find why program does not exit after frame is destroyed

[AlexTZ]

I gather that a wxPython program will not exit if some window (or
other resource?) must be Destroy()'d but has not been.

How can I find what that window/resource is?

More generally, does anyone know how to debug a wxPython program that
does not exit after the main window goes away - occasionally?

[Boštjan Mejak]

For example, if you create a traybar icon using the misfortunately named class wx.TaskBarIcon(), you must explicitly Destroy() that instance of wx.TaskBarIcon() at application exit, otherwise you would see the same effect you are seeing in your application. You must have forget to Destroy() some object that keeps wxPython's main application object alive and kicking.

--
To unsubscribe, send email to wxPython-user...@googlegroups.com
or visit http://groups.google.com/group/wxPython-users?hl=en

[Boštjan Mejak]

Oh yes, you were asking about how to find that window/resource. I hope Robin Dunn will answer that one, too. ;)  I am interested in the answer as well.

[Robin Dunn]

You can use the WIT to get a look at what windows still exist when you
don't expect them to. Or you can just use wx.GetTopLevelWindowList()
and see what is in the list.

--
Robin Dunn
Software Craftsman
http://wxPython.org

[Boštjan Mejak]

Robin, please tell us in what way and where in the application can we use the wx.GetTopLevelWindowList().

>>> import wx

>>> wx.GetTopLevelWindowList()

Traceback (most recent call last):

  File "<stdin>", line 1, in <module>

AttributeError: 'module' object has no attribute 'GetTopLevelWindowList'

[cappy2112]

Try this

import wx
wx.GetTopLevelWindows()

> > To unsubscribe, send email to wxPython-user...@googlegroups.com<wxPython-users%2Bunsu...@googlegroups.com>
> > or visithttp://groups.google.com/group/wxPython-users?hl=en
>
>

[Boštjan Mejak]

Ah, yes, this wx.GetTopLevelWindows() works. Thank you.

or visit http://groups.google.com/group/wxPython-users?hl=en

[Ray Pasco]

wx.Exit() will always force an exit, no matter what, but it may also bypass any wx.EVT_CLOSE handlers you may have added. Also, it does not "exit...the application". It exits the wxPython app.MainLoop(). Whether or not the Python interpreter is also exited is up to what code you have put after the app.MainLoop() statement.

Package wx

"Exit()

Force an exit of the [sic] application. Convenience for wx.GetApp().Exit()"

[C M]

Ray, your comment is not in the thread--again. Did you really click
on "reply" to the previous message?

[Boštjan Mejak]

There's also wx.App.ExitMainLoop() which destroys the wxPython's application object. Not sure if it kills Python application object, too.

On Sun, Oct 17, 2010 at 9:49 PM, C M <cmpy...@gmail.com> wrote:

Ray, your comment is not in the thread--again.  Did you really click
on "reply" to the previous message?

[Ray Pasco]

On Oct 17, 3:49 pm, C M <cmpyt...@gmail.com> wrote:
> Ray, your comment is not in the thread--again.  Did you really click
> on "reply" to the previous message?

Yes, I really did click the [Reply] button this time to reply.

My only guess is that the Firefox browsers I've used (the latest
versions) to send Gmail is somehow messing things up. Firefox has been
self-updating many times in the last few months. I'm currently using
3.6.10.??.??.??

(This reply was sent using Firefox. I will resend using MS IE as an
experiment.)

[Ray Pasco]

This reply is being made using Google Gmail in the MS IE browser to determine whether or not this reply is correctly added to the thread indicated in the email's Subject line or incorrectly creates a new thread.

------------------------------------------------------------------------------------------------------------------

 

Re: "Find why program does not exit after frame is destroyed "

 

http://groups.google.com/group/wxpython-users/browse_thread/thread/f1444d5f37faf196

On Oct 17, 3:49 pm, C M <cmpyt...@gmail.com> wrote:
> Ray, your comment is not in the thread--again.  Did you really click
> on "reply" to the previous message?

 

Yes, I really did click the [Reply] button to reply.

 

My only guess is that the Firefox browsers I've used (the latest versions) to send Gmail is somehow messing things up. Firefox has been self-updating many times in the last few months. I'm currently using 3.6.10.??.??.?? [on Win7].