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 168592 - Tab "Colors" Doesn't has a "Current Status" Tab-Style.
Tab "Colors" Doesn't has a "Current Status" Tab-Style.
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: User Interface
2.2.x
Other Linux
: Low enhancement
: 2.4
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2005-02-26 15:29 UTC by Skot
Modified: 2008-01-15 12:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Skot 2005-02-26 15:29:33 UTC 
Distribution/Version: Gentoo

1. Add the tab called "Colors"
2. Select said tab
3. Open the tab menu
4. Select "Tab-Style"
5. Look in dismay at the entry "Current Status" being grayed out :)

I just updated to Gimp-2.2, and I found strange that this trivial feature was
not added yet, I thought people would had asked for it earlier, but I just
searched all over the Gimp bug database with no relevant feature request.
I would assume this is a very easy thing to implement, and of "minor" importance
for the time being since I currently use the current-status of the Layer tab to
know which are my currently active colors (I removed the
color/Gradient-brush-pattern previews from the toolbox, they were using too much
space....)
Comment 1 Sven Neumann 2005-03-31 12:27:58 UTC 
GimpColorEditor would have to implement GimpDocked::get_preview. With some minor
changes GimpFgBgEditor could be used as the preview widget.
Comment 2 Sven Neumann 2005-03-31 13:39:43 UTC 
2005-03-31  Sven Neumann  <sven@gimp.org>

	* app/widgets/Makefile.am
	* app/widgets/gimpfgbgview.[ch]
	* app/widgets/widgets-types.h: added new widget GimpFgBgView;
	somewhat similar to GimpFgBgEditor but a lot simpler.

	* app/widgets/gimpcoloreditor.c: use GimpFgBgView as preview widget.
	Closes bug #168592.