On Fri, Mar 28, 2003 at 08:29:45AM +0100, Maik Hertha wrote: > > Really? Can't you just use connect() and return True when a double > > click is performed (event.type == gtk.gdk._2BUTTON_PRESS)? > > > Then I need a little assistance. The current situation is: > - - the double-click propagates a button.clicked() signal to raise a dialog-window > - - the dialog-window pops up and is transient to the parent-window.
Sounds pretty normal to me. So it's button_press_event and then window.show(). > At this point I get a X-Server deadlock. This could only be solved Eh? This doesn't sound right. Isn't it just your app that hanged? > with ctrl-alt-backsp. I mention that if the click-signal of the > button is triggered, the function never returns while the dialog is > up. Yes, the dialog would create its own mainloop. In 1.2 this problem > was solved with a w.connect_after(). How to do in 2.0? I think > starting an extra thread is a little bit beyond the goal. A connect_after() to do what? 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/
