perhaps you should catch the event that is suppose to close the window instead of allow the default action (which isn't working for you). Then issue a gtk.main_quit().
By the way it's 'launch' not 'lunch' (which is the mid day meal). Steven Howe p.s. Yes you are ahead of me. I only know a little German. On Wed, 2004-08-04 at 10:54, Le Boulanger Yann wrote: > Hi all, > > I've a probleme with pygtk used in a thread. > My application can be presented like that : I have a main thread that do > some things and that can lunch plugins. Plugins are lunched in a new > thread thanks to threading module. > one of these plugins is a pygtk plugin : > it starts gtk with gtk.gdk.threads_init(), gtk.main(), show windows, etc. > Now the probleme is when I want to close this plugin : I close the main > window, then do a gtk.main_quit(), but the windows opened don't close. > GTK is no more active : I cannot do anything in them, but they are > always here ... > Is it my Job to close them all before the gtk.main_quit() ? > > Asterix > > ______________________________________________________________________ > _______________________________________________ > pygtk mailing list [EMAIL PROTECTED] > http://www.daa.com.au/mailman/listinfo/pygtk > Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/ -- Steven Howe <[EMAIL PROTECTED]> _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
