Thank for the advice.
For now I have resolved with a FileChooserDialog, but I will try to
customize a gtk.Dialog to fit my need.
Mauro
Paul Pogonyshev ha scritto:
Mauro Giacomini wrote:
I have a problem with the set_modal function in a pygtk program I'm writing.
The situation:
I have a main window; when the user clicks on a button, a new window
came up for the selection of a particular item in a treeview.
When the user confirm the selection with the click on the "ok button",
this window disappear (destroy) and the interaction return to the main
window.
But, although I declare the second window such as modal window and
transient for main window, the instruction I put in the main window
after the call to the second window are executed without waiting the
response for the second window.
Is there something else to do?
Or is there a better approach to a similar situation?
Modality itself only prevents user from interacting with other
application windows. It doesn't cause application to wait for window
response anywhere. If you want to get response "now", use
gtk.Dialog.run().
Note that GNOME programs are generally not recommended to use modal
windows.
Paul
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://faq.pygtk.org/
