On Sun, Feb 08, 2004 at 11:20:49PM -0500, John K Luebs wrote: > On Sun, Feb 08, 2004 at 12:59:44PM -0800, Jeff Bowden wrote: > > Antoon Pardon wrote: > > > > > >My idea to handle this would be to create a new signal. Have a handler > > >for this signal in the gui thread and let the background task emit this > > >signal. Would this be workable? On Windows? > > > > > > > > > > > > > I'm not sure if that even works on Linux. I haven't traced down the > > code path but it wouldn't surprise me if emit ends up executing > > synchronous calls to the connected signal handlers. Is this documented > > somewhere? Am I wrong? > > You're correct, the signal handler will end up being handled in the > thread that calls emitted. Signals are not queued asynchronously or > anything. I'm not sure where this is documented but it goes along > with the overall thread agnostic design of GTK+.
But FAQ 20.1 says: Signal callbacks will be done in the main thread. If I understand you correctly emiting a signal is the same as calling the handler directly. -- Antoon Pardon _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
