After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 433445 - gtk.FileChooserDialog no longer sets filenames correctly
gtk.FileChooserDialog no longer sets filenames correctly
Status: RESOLVED NOTABUG
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.10.x
Other All
: Normal normal
: ---
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2007-04-25 21:39 UTC by Josselin Mouette
Modified: 2007-04-30 16:01 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Josselin Mouette 2007-04-25 21:39:04 UTC 
[ forwarded from http://bugs.debian.org/420698 by Joe Wreshnig ]

Since upgrading to PyGTK 2.10.4 (from a 2.8 version) one of Quod Libet's unit tests is failing due to this problem:

$ python -c "
import gtk
chooser = gtk.FileChooserDialog()
chooser.set_current_folder('/home') # this does return True
print chooser.get_current_folder()"
None

This worked in GTK 2.8 (i.e. chooser.get_current_folder() returned "/home").
Comment 1 Johan (not receiving bugmail) Dahlin 2007-04-25 21:41:10 UTC 
PyGTK does nothing special here.
Moving over to Gtk+.
Comment 2 Matthias Clasen 2007-04-26 04:24:10 UTC 
This is due to the fact that most filechooser operations are now asynchronous.
Comment 3 Josselin Mouette 2007-04-30 13:35:58 UTC 
Yes, the filechooser now returns the current folder only after successfully loading it, but it breaks the former semantics. It would make sense, when impl->current_folder is null, to return the path in update_current_folder_handle if there is one.
Comment 4 Federico Mena Quintero 2007-04-30 16:01:31 UTC 
Unit tests written like that will fail.  The file chooser loads folders asynchronously, and doesn't report the loaded folder until it has ensured that it was able to load it.