FAQ item 20.8 applies only to 2.X right? gtk.threads_init() doesn't seem to be wrapped in 0.6.X and it looks to me like the thread initialization will be done in the C module code.
I've never had success using gtk.threads_enter() and threads_leave() and have had to resort to making sure all GTK code is in the main thread.
Hi Steve,
I'm working with pygtk 2.2.0 and python 2.3.3. Threading works fine in most cases. Call gtk.threads_init() before gtk.main(). Most of my gtk code runs in the main_thread. When I want to do some gtk-stuff from another thread, I wrap those lines in a gtk.threads_enter() and gtk.threads_leave() pair. That's it.
The only problem I left is combining PyOpenGL or PyGtkGLExt with python threads. When doing GL calls from a thread that is not in the main thread, the application crashes.
(On what does the version number 0.6.X apply? I don't get your point there.)
regards,
Toon _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
