On Tue, 5 Dec 2000, James Henstridge wrote:
> I don't handle signals properly in pygtk at the moment. The correct
> solution to get the signals handled is to make sure
> Py_MakePendingCalls() is called regularly. This could be done through an
> idle or timeout handler in the case of pygtk.
>
> I am not sure how to get CORBA.ORB.run() to do a similar thing though.
Apart from modifying ORBit itself, (pardon my ignorance) would using
SIGALRM be an idea? I'm sure ORBit doesn't use it for anything else, and I
surmise Python's Handlers[] would stay untouched. I do think I'd have the
same trouble with calling the handler for SIGALRM itself, however, since
I'd have to clobber Python's signal_handler for it.
Apart from that, I can see no way myself. I could reattach a custom
handler to all signals, but how would I set the signals as triggered
_themselves_? At any rate, thanks for the answer.
Take care,
--
/\/\ Christian Reis, Senior Engineer, Async Open Source, Brazil
~\/~ http://async.com.br/~kiko/ | [+55 16] 274 4311
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
