Hope I solved my problem and somebody could me explain why.
I have a button_press_event connected with a connect_after to a clist. The callback should have a look if there is an already selected row and the event was triggered by a left mouse double click. If so it raises a signal to popup a dialog window. In 0.6.x this runs fine. After upgrading this app to 1.99.(>14) the connect_after doesn't work. Why was explained by James in this thread. A simple switch from connect_after to connect was not possible. Because there is a deadlock after the dialog is shown ((python)app, gtk.mainloop, X-server).
I played a little bit without sense and found that the following combination does work, but
I don't know why? I put the signal propagation in a idle-hanlder and it works.
--- snip
def onRowBtn2Clicked(self, clist, ev):
''' verarbeitet doppelklicks auf die zeilen '''
print clist.selection, ev.button, ev.type
if not clist.selection:
return FALSE
data = clist.get_row_data( clist.selection[0] )
if ev.button == 1 and ev.type == 5:
#self.set_options_button.clicked()
gid = gtk.idle_add( self.set_options_button.clicked )
print gid
return FALSE
---/snipShould I remove the idle-handler after closing the dialog window? /
--
mit freundlichem Gru� / best regards
Maik Hertha
--------------------------------------------------- h+h
EBSP Anwenderbetreuung, +49 5361 9-74950
Volkswagen AG / Brieffach 1721 / D-38436 Wolfsburg
http://ebsp.wob.vw.de maik.hertha at volkswagen dot de
---------------------------------------------------
hartmann+hertha
it (beratung / entwicklung / support)
http://www.hartmann-hertha.de
mhertha at hartmann-hertha dot de
--------------------------------------------------- h+h
_______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
