|
From: Jeff H. <je...@ac...> - 2007-11-28 19:47:20
|
Kevin Partin wrote: > Currently when the user presses a button on a ttk::dialog widget, the > widget is destroyed regardless of which button was invoked, and the > return status of the callback command. > > In terms of user feedback and interaction with the dialog widget, > wouldn't it be better if the command where executed before the dialog > widget is destroyed? The dialog widget could check the return status of > the command, and if it was zero, destroy the dialog. This way the > programmer has some control over when the dialog is destroyed. > > To accomplish this task now, I don't specify a '-command' option when I > create the dialog, and configure the dialog button commands after the > dialog is created. > > Just a thought. I don't know if this topic has been previously > discussed. I agree, but this and other points is why ttk::dialog is not in 8.5 core. You can look at widget::dialog for ideas on how to handle the richer possible interactions with a dialog. It is more of a replacement for a general dialog shell, whereas ttk::dialog tries to be a richer tk_dialog. Jeff |