On Tue, Apr 01, 2003 at 12:37:16PM +0200, Herr Maik HERTHA wrote: > > 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.
idle_add() just makes your callback run when the GTK+ mainloop is idle. In your case it makes sense since you want to open the popup last. However, in your case I honestly don't think this complication is at all justified. If all you want to do is pop up a dialog window on double-click, why don't you just check double-click, select the row your event object is positioned over, and show the dialog? Why do you need to use two callbacks chained? It's too weird for me. > Should I remove the idle-handler after closing the dialog window? No, idle handlers are only executed once, differently from timeout handlers. Take care, -- Christian Reis, Senior Engineer, Async Open Source, Brazil. http://async.com.br/~kiko/ | [+55 16] 261 2331 | NMFL _______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
