Yes, I can. I have a lot of trouble maintainig the code with those constructs.It is my approach of event-driven applications. There is only one responsible callback to show the dialog.
See, I don't understand what you mean by this. Why can't you have a
method called show_dialog() which is called by N different callbacks?
One of them could be a double-click on the row, another could be a
menuitem you select, etc.
But consider you have 4 entrypoints to show the dialog - MenuItem, KeyStroke (Shortcut),
Button, 2ButtonClick and you attach an extra data field on the button-widget (w.set_data(...)).
There is a lot more extra work for the show_dialog()-method as the arguments are different
for each call. And there is the problem with the w.get_data(..)-method which is bound to
the button. My opinion is, it is much easier to propagate a button.clicked-signal than maintaining
extra code. Each time you enhance your application you have to modify the show_dialog-method.
I need only an extra clicked-signal.
Thank you for your help. --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 [EMAIL PROTECTED]
---------------------------------------------------
hartmann+hertha
it (beratung / entwicklung / support)
http://www.hartmann-hertha.de
[EMAIL PROTECTED]
--------------------------------------------------- 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/
