On Tue, Apr 01, 2003 at 12:37:16PM +0200, Herr Maik HERTHA wrote:It is my approach of event-driven applications. There is only one responsible callback to show the dialog.
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.
If you only select the row and use the button it is clear. But if I define a "short-cut-action" for the user this
dialog should be raised by the same signal. So I transform this event in the equal app-signal "button-was-clicked".
On a MSWindows box you send a message. On Unix I use this "event-signal-transformation".
Are there better approaches? Thank you for your reply.
Cheers. --maik./
--
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/
