fre 2004-03-26 klockan 14.01 skrev Christian Robottom Reis: > On Thu, Mar 25, 2004 at 06:49:25PM -0800, Andrew P. Lentvorski, Jr. wrote: > > Problem #2 is the unblocking without events. This appears to be a PyGtk > > issue. Even though Gtk returns the wrong value for gtk_main_iteration(), > > it does block correctly. It appears that PyGtk adds some flavor of event > > timer which causes the event loop to kick loose every .1 seconds. > > Hmmm. Could this be the workaround/hack that was added to handle signals > while in the mainloop? IIRC this is how ctrl-C was allowed to break the > mainloop. Am I remembering correctly, Johan?
Right, I added that (which is sort of hackish) to be able to make python events (eg KeyboardInterrupts) to be send be triggered. So, we need to add a sanity check in there somewhere I guess. -- Johan Dahlin <[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/
