The documentation claims that the "dialog" property of the
FileChooserButton is writeable. I have not tested this, but could
you create the FileChooserButton and then create your own
FileChooserDialog and assign it to the FileChooserButton? Then you
could attach to the "response" or "close" signals of your dialog.
Let me know if this works.
Phillip Calvin
On Jun 22, 2007, at 3:37 AM, Jamie Norrish wrote:
Hi there. Back in February Felix Rabe asked about how to know when a
FileChooserButton's associated dialog is closed (so that the filename
of the selected file can be retrieved from it). As far as I can see,
there was no particular response. Having now stumbled upon the same
issue, does anyone have any answers?
As Felix noted, the file-activated signal does not appear to be the
correct one - I could not get it to fire no matter what I did in the
dialog - and the documentation is not forthcoming about what one
should use, only that one shouldn't normally need to connect to any of
the signals (!).
Jamie
--
Artefact Publishing: http://www.artefact.org.nz/
GnuPG Public Key: http://www.artefact.org.nz/people/jamie.html
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
_______________________________________________
pygtk mailing list [email protected]
http://www.daa.com.au/mailman/listinfo/pygtk
Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
