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 481002 - remember last location for "save as", "save a copy", "save", "open"
remember last location for "save as", "save a copy", "save", "open"
Status: RESOLVED DUPLICATE of bug 310220
Product: GIMP
Classification: Other
Component: User Interface
2.3.x
Other All
: Normal minor
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2007-09-27 16:00 UTC by firepol
Modified: 2016-12-08 16:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description firepol 2007-09-27 16:00:34 UTC
E.g. I open an image stored in /media/graphics/work/animals/cat/mycat/christmas/cat.jpg

Now, if I cut a part of the image and I paste it into a new image, then I click "save as" I get as default my home directory (in my case /home/paul/) which is very annoying since I'd like to saved the modifed image in the same folder (last location) I've just opened a few seconds before. I need to re-navigate the whole tree to select the directory, loosing a bunch of time.

The usability improvement I', suggesting is to always remember the last location where the user opened or saved a file.

E.g. I open a file from /media, then I manipulate it and create a new image fom it, I save as I should be already in /media/graphics.
If I create a folder "temp" and save the file there, then click "open" I'd like to be aleady in /media/graphics/temp (last location)... see what I mean?

Please do this improvement. I'm talking about saving a lot of clicks and time to the users.

Other information:
Comment 1 Sven Neumann 2007-09-27 19:04:27 UTC
Might make sense to discuss this again with the usability experts on the mailing-list. Bugzilla is not the right place for such discussion though. Closing as duplicate of bug #310220.

*** This bug has been marked as a duplicate of 310220 ***