Not sure what’s happened - too much testing/changes - but, whereas it worked before, my class that inherits from wx.Frame is now no longer killing it’s process when I use self.Close() and even if then include self.DestroyChildren() and self.Destroy(), if I am running it from python interpreter, the process just stays running, and if I build it using cx, then, while it disappears from screen, if I look in windows task manager, the process of the executable is still running…?
Can pass on code, but, it’s still newish code, and not sure what have added/changed recently to cause this to start happening now.
Thoughts/suggestions what to look for/try?
TIA
Jacob Kruger
Blind Biker
Skype: BlindZA
“Roger Wilco wants to welcome you…to the space janitor’s closet…”
I'd look for other top level windows (frames, dialogs)
which have not had their Destroy function called after
use.
Karsten
···
On Fri, Mar 14, 2014 at 12:31:47PM +0200, Jacob Kruger wrote:
Not sure what's happened - too much testing/changes - but, whereas it worked before, my class that inherits from wx.Frame is now no longer killing it's process when I use self.Close() and even if then include self.DestroyChildren() and self.Destroy(), if I am running it from python interpreter, the process just stays running, and if I build it using cx, then, while it disappears from screen, if I look in windows task manager, the process of the executable is still running..?
Can pass on code, but, it's still newish code, and not sure what have added/changed recently to cause this to start happening now.
Thoughts/suggestions what to look for/try?
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
A timer not stopped or using a TaskBarIcon and not destroy it (see
self.tbicon in the wxPython demo)
Werner
···
Hi,
On 3/14/2014 11:31 AM, Jacob Kruger wrote:
Not sure what's happened - too
much testing/changes - but, whereas it worked before, my class
that inherits from wx.Frame is now no longer killing it’s
process when I use self.Close() and even if then include
self.DestroyChildren() and self.Destroy(), if I am running it
from python interpreter, the process just stays running, and
if I build it using cx, then, while it disappears from screen,
if I look in windows task manager, the process of the
executable is still running…?
Can pass on code, but, it's still
newish code, and not sure what have added/changed recently to
cause this to start happening now.
Thoughts/suggestions what to look
for/try?
Ok, got it - think was a good thing to take a break, and get away from PC for a little while - had almost forgotten had a separate thread running in background, and while had it watching a trigger boolean value to tell it to exit the thread when I wanted to close whole app, had forgotten that had set it's operating time interval to 30 seconds, and was only waiting 0.5 seconds after changing that boolean value, before trying to Destroy() main process.
Funny enough had also tried firing up the inspection tool to see if could track down a process/object/element like that, but, that was literally making my whole machine seem to hang when fired up code - maybe will try turning off background thread and see if that still happens - just in case there's something else am missing/have forgotten about.
Stay well
Jacob Kruger
Blind Biker
Skype: BlindZA
"Roger Wilco wants to welcome you...to the space janitor's closet..."
···
----- Original Message ----- From: "Karsten Hilbert" <Karsten.Hilbert@gmx.net>
To: <wxpython-users@googlegroups.com>
Sent: Friday, 14 March, 2014 12:37 PM
Subject: Re: [wxPython-users] Killing process, etc.
On Fri, Mar 14, 2014 at 12:31:47PM +0200, Jacob Kruger wrote:
Not sure what's happened - too much testing/changes - but, whereas it worked before, my class that inherits from wx.Frame is now no longer killing it's process when I use self.Close() and even if then include self.DestroyChildren() and self.Destroy(), if I am running it from python interpreter, the process just stays running, and if I build it using cx, then, while it disappears from screen, if I look in windows task manager, the process of the executable is still running..?
Can pass on code, but, it's still newish code, and not sure what have added/changed recently to cause this to start happening now.
Thoughts/suggestions what to look for/try?
I'd look for other top level windows (frames, dialogs)
which have not had their Destroy function called after
use.
Karsten
--
GPG key ID E4071346 @ gpg-keyserver.de
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.