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 301348 - Remove the close buttons from dockables
Remove the close buttons from dockables
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: User Interface
git master
Other All
: Normal enhancement
: 2.4
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-04-20 15:24 UTC by Michael Schumacher
Modified: 2005-04-21 23:30 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
patch that removes the close buttons from all dockables (7.08 KB, patch)
2005-04-21 14:27 UTC, Sven Neumann 		none Details | Review

Description Michael Schumacher 2005-04-20 15:24:25 UTC 
The close buttons in the dockable titles (directly besides the dockable menu
button) seem to server only one purpose: confusing new users when being hit by
accident. It is a lot harder to add e.g. the tool options back than to remove
them - and this dockable can be considered vital for GIMP usage. 

Even after removing the close button it is rather easy to remove a tabbed
dockable - either use the menu or drag it out and close the dialog.
Comment 1 Sven Neumann 2005-04-20 18:08:39 UTC 
I tend to agree with Michael here. The tab can be closed using the "Close Tab"
item in menu. Closing dockables out of the notebook is also not something that
is frequently needed.
Comment 2 Sven Neumann 2005-04-21 14:27:02 UTC 
Created attachment 45519 [details] [review]
patch that removes the close buttons from all dockables
Comment 3 Michael Natterer 2005-04-21 19:56:43 UTC 
Looks even better and less cluttered without. Let's just remove it.
Comment 4 Sven Neumann 2005-04-21 23:30:52 UTC 
2005-04-22  Sven Neumann  <sven@gimp.org>

	* app/widgets/gimpdockable.[ch]: removed Close button from
	dockables as suggested in bug #301348.