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 432763 - File Save dialog confusing for first-time users who don't know image types
File Save dialog confusing for first-time users who don't know image types
Status: RESOLVED DUPLICATE of bug 165684
Product: GIMP
Classification: Other
Component: User Interface
2.2.x
Other All
: Normal minor
: 2.4
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2007-04-23 21:35 UTC by Daniel Kahn Gillmor
Modified: 2008-01-15 13:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Kahn Gillmor 2007-04-23 21:35:35 UTC
The File Save dialog box is confusing for a new user who doesn't understand file extensions, particularly when they are editing a new image.

Consider the following steps as a reasonably bold new user of the GIMP:

Launch the GIMP

See nothing to edit.  By analogy with other GUI apps, choose File|New from the menu of the main window.  Click "OK" in the dialog box that pops up.

Make a couple changes to the new canvas presented, and then (also by analogy with other GUI apps) choose File|Save from the menu on the canvas.

Give your new image a name (or stick with "untitled") and click "Save".  An error message "Saving '/home/myusername/Untitled' failed: Unknown file type"

As an experienced user, or someone who has knowledge of file extensions, this makes sense.  As a new user, it might be frustrating to not know how to save an initial document.

I suggest: If the image currently has no filetype associated with it, and the user doesn't put in an extension, and "save by extension" is selected (as i think it is by default, at least on debian etch), automatically save as an XCF, and append the .XCF extension.
Comment 1 Michael Schumacher 2007-04-24 08:30:03 UTC
I think this is a duplicate of bug #165684.
Comment 2 Michael Natterer 2007-04-24 08:43:37 UTC
Indeed it is.


*** This bug has been marked as a duplicate of 165684 ***
Comment 3 Daniel Kahn Gillmor 2007-04-24 14:54:45 UTC
Thanks for the pointer to that bug.  I agree that it's the same one.  Sorry that i didn't find it when i searched initially.  I'm glad to see it's planned for GIMP 2.4.

I just pulled the development version 2.3.15-1 from debian experimental to try it out, and it does resolve the described problem.

Thanks for all your work on this.  I look forward to the release of GIMP 2.4!