> According to <http://wiki.tcl.tk/10014> it waits for the window to be > destroyed. Why do you ask?
Hi Russell, I realise that, but if I just don't call it and return control to the mainloop then much the same thing will happen anyway (i.e. the application will wait for events in the window concerned and respond to them appropriately) All the examples I can find for it are in the context of a modal dialog but "grab_set" causes dialogs to be modal with or without "wait_window". I'm trying to understand some code I've inherited and getting some funny race conditions which I can't really pin down, related to calls to after_idle. They seem to go away if I remove the call to wait_window so I'd like to get my head round what the point of calling it is. The code looks much like the sample code (tkSimpleDialog.py) at http://effbot.org/tkinterbook/tkinter-dialog-windows.htm and in fact may even have been copied from there. Regards, Geoff _______________________________________________ Tkinter-discuss mailing list Tkinter-discuss@python.org http://mail.python.org/mailman/listinfo/tkinter-discuss
