> GMainLoop/GMainContext > > It's now possible to run the GMainLoop without importing gtk. > This is very useful for projects that only uses input_add, > timeout_add or idle_add. > > Threading > > A lot of work has been gone into improving and testing > threading support in PyGTK. It should now be possible to use > threads in most situations. There are a few limitations however, > For instance, the mainloop will always be run in the main thread.
With regards to these previous paragraphs, If I create a thread that basically waits for a socket useing gtk.input_add, can I use GMainLoop in the thread and not interfere with the main app running main loop or will the input_add still be called when the mainlopp from the main app is ready? Did that make sense? Basically is there any point in breaking off something that uses input_add or timeout_add or idel_add into it's own thread or will these simple hang about waiting on the thread that calls gtk.mainloop() -- * Rob Brown-Bayliss * ================= * zoism.org _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
