Gimp 2.2.2 file open/save dialogues

mbeattie74 · 01-16-2005, 04:11 AM

Since upgrading to Gimp 2.2.2 the file open/save dialogues have developed Alseimer's disease - they forget the last accessed directory.

Previously, files could be loaded from one directory, processed, and then saved in a different directory. The next time the file open dialogue was accessed it would remember the previous directory, and then when it is saved it would remember the different destination folder.

Now every time a file is opened it defaults to /usr/home/[username], while the destination directory it seems to remember.

Does anyone else have the same problem? I'm not sure that it's Gimp sepecific - it may be a gnome issue as it started happening for me after an "apt-get upgrade" which has caused some other gnome apps to exhibit the same behaviour.

cheers

reddazz · 01-16-2005, 07:56 AM

Yeah, I have the same problem, I can't seem to get it to remember the current working directory and everytime I try to save something I am taken to /home/userid instead of the last directory from which an image was open.

mbeattie74 · 01-16-2005, 06:45 PM

Sorry about the delay - time zone difference: Japan.

Has it allways been like that reddazz, or did it only start behaving this way recently? I'm still not sure whether it's the Gimp specifically or something more central to Gnome itself. I think I've also caught Screem showing similar symptoms.

reddazz · 01-16-2005, 07:21 PM

I think it started when I upgraded to gimp 2.2.x. when they began using the default GNOME open/save dialogue.

mbeattie74 · 01-16-2005, 07:46 PM

That might explain other Gnome apps showing similar behaviour if they also use the default Gnome file selector.

Someone on the Gimp User Group forums had this to say:
"Well, the old file-selector definitely was broken beyond the point where it could have been repaired. If you think there are issues with the new file-chooser widget, please report them. So far however you didn't mention anything that hasn't already been reported. "
http://gug.sunsite.dk/forum/?threadid=2539

The "new file-choose widget" - what, you mean the one that's built into Gnome? hmmm... I think I'd prefer the old "broken" one thank you, at least it was useable

I thought Gnome was all about HID guidelines?

reddazz · 01-17-2005, 01:19 AM

It's good to have a HIG framework, if you then create apps that work properly within that framework. Unfortunately for GNOME it's not the case, sometimes I believe they spend so much time discussing HIG's than creating a good user desktop. Ever since GNOME 2.x, there has always been some major component thats broken or doesn't work properly e.g. the file open/close dialogue, gstreamer etc. Just hope they put their act together for the next release.

mbeattie74 · 01-17-2005, 01:35 AM

Let's hope so. What would be great would be a "grand unified desktop" so to speak, something which allows the user to pick and choose their preferred applications from both (gnome/kde) desktops while providing an 3rd party desktop shell. I know I for one have a list of apps which I use on a daily basis and can't live without which is comprised of programs from both. I'm keeping a close eye on enlightenment.org for DR17 to come out and in the meantime putting up with broken file open/save dialogues etc.

cheers

daihard · 01-17-2005, 04:14 AM

I'm having the same issue with Gnome 2.2.1, which I compiled myself a couple of weeks ago. I am using GTK 2.4.7. Is it possible that newer versions of GTK may have it fixed?

mbeattie74 · 01-17-2005, 06:24 AM

My libgtk2.0-0 is version 2.4.14-2, which seems to be a later version.

I've been using Gnome 2.8 since the binaries appeared via Debian's package repositories, but these woes only began a week or two ago after one of the Gimp 2.2.X version iterations (bugfixes), 2.2.1 to 2.2.2 I think.

reddazz · 01-17-2005, 06:30 AM

I am using gtk 2.6.1 and the problem is still there, so upgrading you version of gtk at this moment may not be entirely helpful.

mbeattie74 · 01-18-2005, 07:00 PM

Well, the upside of this is that I've re-aquianted myself with an old friend - the command line.

These new and improved annoyances were making it impossible for me to maintain a photoblog, which requires images to be resized from their native 5.4Mpixel resultion down to sensible sizes for the web, which is infuriating if your image editor forgets which directory you were using between each and every image.

To the rescue comes ImageMagick and it's command line batch processing!
It's good - http://www.imagemagick.org