On Wed, 12 Mar 2003, Jon Nelson wrote: > On Wed, 12 Mar 2003, Christian Reis wrote: > > .. > > Well, calling mainiteration *inside* a callback is bound to be tricky > > and produce races and deadlocks. I'm not sure ig gtk2 handles this > > better, but maybe some gtk2 ninja can step up and give you the ultimate > > reason to upgrade? :-) > > > > I don't know of any way to block a callback that doesn't use > > emit_stop_by_name() and in your case it's not applicable (since you're > > not using signals). There's also signal_handler_block, etc, but do you > > get an ID back when you do input_add? > > OK, signal_handler_block is an object method. Which object should I use?
Well, using the top-level window is no good: Gtk-WARNING **: gtk_signal_handler_block(): could not find handler (55) Of course, without the other mechanisms in place, it still hangs. :-( Just to be sure, I tried (again) using input_remove, etc... No go. -- "Never try to write to ROM - it wastes your time and annoys the ROM." Jon Nelson <[EMAIL PROTECTED]> C and Python Code Gardener _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
