Ter, 2005-12-13 às 04:04 +0100, dannym escreveu:
Hi,
Am Donnerstag, den 01.12.2005, 12:23 + schrieb Gustavo J. A. M.
Carneiro:
[...]
You need to call dialog.destroy(). del dialog doesn't work because
gtk+ itself always keeps one last reference to toplevel windows until
you
Hi,
Am Donnerstag, den 01.12.2005, 12:23 + schrieb Gustavo J. A. M.
Carneiro:
[...]
You need to call dialog.destroy(). del dialog doesn't work because
gtk+ itself always keeps one last reference to toplevel windows until
you destroy() them (or until they are implicitly destroyed by
On Mon, 2005-11-28 at 22:47 +0100, dannym wrote:
Hi,
Am Montag, den 28.11.2005, 15:47 -0500 schrieb Graham Ashton:
On Monday 28 November, dannym wrote:
Usually you just use a modal event loop:
dialog = gtk.FileChooserDialog()
answer = dialog.run() # hangs around until dialog
Hi,
Am Dienstag, den 22.11.2005, 14:37 -0500 schrieb Thierry Lam:
Does anyone know how to set modal to True for Gtk::FileChooserDialog?
Usually you just use a modal event loop:
dialog = gtk.FileChooserDialog()
answer = dialog.run() # hangs around until dialog is closed
del dialog
On Monday 28 November, dannym wrote:
Usually you just use a modal event loop:
dialog = gtk.FileChooserDialog()
answer = dialog.run() # hangs around until dialog is closed
del dialog
Hi. Wouldn't it be better to say:
dialog.destroy()
instead of
del dialog
?
It was a long time ago
Hi,
Am Montag, den 28.11.2005, 15:47 -0500 schrieb Graham Ashton:
On Monday 28 November, dannym wrote:
Usually you just use a modal event loop:
dialog = gtk.FileChooserDialog()
answer = dialog.run() # hangs around until dialog is closed
del dialog
Hi. Wouldn't it be better to
Does anyone know how to set modal to True for
Gtk::FileChooserDialog?
Thanks
Thierry
___
pygtk mailing list pygtk@daa.com.au
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
