-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > > >The difference to the 0.6.x code is, that I include the return > >statements in the functions with FALSE. If I do a > signal_connect I get > >a deadlock situation with the dialog window which is called via > >Set_options_button.clicked(). > > > >Could it be a bug anyway ? > > > > > The behaviour was implemented in GTK 2.0. It is different to > GTK 1.2, > but it is not considered a bug. > > James. > If it's not a bug, how I have to handle connect and connect_after signals on the same widget. As Stephen mentioned, the connect_after isn't called anyway on normal situations (like 0.6.x).
Thanks for the help. - --maik./ mit freundlichem Gru� / with best regards Maik Hertha - -------------------------------------------- hartmann+hertha it design [EMAIL PROTECTED] http://www.hartmann-hertha.de - -------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) iD8DBQE+fXNybd3QGXGos6ERAjbqAKCChhwgz9ACIINAuF0u8zp+qZqY/ACg4xR1 4s90EPz1z8UDv//UQuthoWs= =RXKz -----END PGP SIGNATURE----- _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
