On Tue, 29 Jul 2003, Christian Reis wrote: > > the following, which works except that a warning is logged if the handler > > is disconnected before _disconnect_callback() is invoked (because > > disconnect is called multiple times with the same handler id). > > Store a list of connected handler ids, and remove the id when > disconnected. All you need to do is then check if the id is present > before calling disconnect. That should avoid the warning.
That would work but it would further complicate things, particularly since the _disconnect_callback() is a generic function. I suppose I could maintain a list of connections and then implement my own disconnect() function that would remove things from the list, but then I'd need to call that disconnect function rather than the disconnect method. It might be better to add some method to check to see if the handler is still connected and only call disconnect if it is. Does a function to check if a handler is connected exist in the C api? Thanks, John _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
