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 142624 - improve close confirmation dialog
improve close confirmation dialog
Status: RESOLVED DUPLICATE of bug 106726
Product: GIMP
Classification: Other
Component: User Interface
2.0.x
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2004-05-16 19:17 UTC by Paolo Borelli
Modified: 2004-05-17 09:15 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Paolo Borelli 2004-05-16 19:17:02 UTC
The confirmation dialog showed when trying to quit with unsaved images can be
improved in various aspects. In difficulty order:

- HIG compliance (primary/secondary text)
- should at least have a Save button
- In case there is more then one unsaved images a list with checkbotton should
be displayed in the dialog.


To have a look at what I mean, gedit 2.6 includes all the above features
(especially the third)
Comment 1 Sven Neumann 2004-05-17 08:52:44 UTC
This is basically a duplicate of bug #106726.
Comment 2 Paolo Borelli 2004-05-17 09:02:54 UTC
oh...ok. I missed it since the summary of 106726 is misleading. Maybe it's
better to keep the two bugs separate since a "Close All" menu item is separate RFE.

If you instead prefer to track the two issues together, fine with me. In that
case  is maybe worth adding to that bug the reference to gedit since I'm
confident that a chunk of code could be easily reused.
Also in that bug is not noted that the dialog is not HIG compliant.
Comment 3 Sven Neumann 2004-05-17 09:15:29 UTC
Well, none of the GIMP 2.0 dialogs are HIG compliant and they aren't supposed to
be. There's another report about HIG compliance that is targetted for the 2.2
release.

I also don't think we need to copy any code from gedit. Coding the dialog layout
is the smallest problem here. I guess it's better we track this issue in one
place, closing as duplicate.

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