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 702343 - In single-window mode, clicking the window's close/quit button should quit the app
In single-window mode, clicking the window's close/quit button should quit th...
Status: RESOLVED DUPLICATE of bug 664584
Product: GIMP
Classification: Other
Component: User Interface
2.8.4
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2013-06-15 15:25 UTC by Jean-François Fortin Tam
Modified: 2013-06-17 21:02 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jean-François Fortin Tam 2013-06-15 15:25:13 UTC
Currently, clicking the X in the global window only closes the current active image.

So if you have two images open in tabs, to exit the program you have to click the X three times: clicking once closes the active tab, clicking twice closes the remaining image tab, and then... you're left with a gimp instance with no image and have to click a third time to quit the application.

Instead it should just quit the application (close all the tabs and exit) the first time I click on that global X button. This would be consistent with other apps (Nautilus, Epiphany, Firefox, Gnumeric, Gedit, you name it). If there are unsaved changes, then do prompt the user about them before quitting.

If I want to close an individual image/tab, I'd use the close button on the actual image's tab (similar to the other tabbed interfaces I've seen).


Thanks :)
Comment 1 Michael Schumacher 2013-06-15 18:12:13 UTC
This is probably a duplicate of bug #664584.
Comment 2 Michael Natterer 2013-06-17 21:02:32 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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