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 598974 - A newly created folder is not shown in "save as" dialog
A newly created folder is not shown in "save as" dialog
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: User Interface
2.6.6
Other Mac OS
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2009-10-19 18:51 UTC by Ingo Schaefer
Modified: 2009-10-22 20:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Ingo Schaefer 2009-10-19 18:51:29 UTC 
When saving an image to file, there is a "Create Folder" option in the dialog.

If a new folder within the current directory is created with this button, the directory content is not refreshed, so the new created folder is not seen by the user.

One has to explicitely leave the current folder and enter it again to see this created folder.
Comment 1 Sven Neumann 2009-10-19 21:39:29 UTC 
That would be a bug in GTK+ or GLib then. What versions of these libraries are you using?
Comment 2 Ingo Schaefer 2009-10-20 18:07:58 UTC 
Tell me, how to find it out.

I can not find any file containing gtk+ in the filename using find inside the MacOSX application folder. Searching for files containing gtk brings:
./Contents/Resources/etc/gimp/2.0/gtkrc
./Contents/Resources/etc/gtk-2.0
./Contents/Resources/etc/gtk-2.0/gtk.immodules
./Contents/Resources/etc/gtk-2.0/gtkrc
./Contents/Resources/lib/gtk-2.0
./Contents/Resources/lib/libgtk-x11-2.0.0.1400.7.dylib
./Contents/Resources/lib/libgtk-x11-2.0.0.dylib
./Contents/Resources/lib/libgtk-x11-2.0.dylib
./Contents/Resources/lib/libgtkglext-x11-1.0.0.0.0.dylib
./Contents/Resources/lib/libgtkglext-x11-1.0.0.dylib
./Contents/Resources/lib/libgtkglext-x11-1.0.dylib
./Contents/Resources/lib/libgtkimageview.0.0.0.dylib
./Contents/Resources/lib/libgtkimageview.0.dylib
./Contents/Resources/lib/libgtkimageview.dylib

plus several python bindings, messages and so on.

Looking for glib gives:
./Contents/Resources/lib/libdbus-glib-1.2.1.0.dylib
./Contents/Resources/lib/libdbus-glib-1.2.dylib
./Contents/Resources/lib/libdbus-glib-1.dylib
./Contents/Resources/lib/libglib-2.0.0.dylib
./Contents/Resources/lib/libglib-2.0.dylib
./Contents/Resources/lib/libpoppler-glib.4.0.0.dylib
./Contents/Resources/lib/libpoppler-glib.4.dylib
./Contents/Resources/lib/libpoppler-glib.dylib
Comment 3 Daniel Macks 2009-10-22 18:09:55 UTC 
libgtk-x11 is one of the libraries in the GTK+ suite.
Comment 4 Daniel Macks 2009-10-22 18:20:15 UTC 
I fail to reproduce this using fink's gimp (built from sources 2.6.6) using gtk (built for x11 from sources version 2.16.6) on osx 10.4/ppc. Save As...New Folder creates the folder in the file-list with the name as an editable field, and then it's there for me to use.

Based on the file listing in Comment #2, reporter is using an .app bundle, probably downloaded precompiled as a .dmg installer. libgtk-x11 filename 1400.7 corresponds to gtk version 2.14.7.

Sounds like 1) a gtk not gimp issue using 2) an unknown-provenance binary that is 3) an old version.
Comment 5 Sven Neumann 2009-10-22 20:08:22 UTC 
Yeah, let's close it as OBSOLETE then. Bug reports against binaries for the Mac should anyway always first be reported to the packager of the binary.