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 97616 - Confusing that "pallette editor" is used to select colors from pallettes
Confusing that "pallette editor" is used to select colors from pallettes
Status: RESOLVED DUPLICATE of bug 346884
Product: GIMP
Classification: Other
Component: User Interface
git master
Other other
: Normal enhancement
: 2.6
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2002-11-04 09:06 UTC by Jim Meier
Modified: 2006-08-07 14:44 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jim Meier 2002-11-04 09:06:27 UTC
The palette tab/dialog lets you select, edit, and create palettes, but I
cannot find a place to choose colors from the current palette.

This is probably as simple as the 'select' tab of the 1.2 palettes dialog
not being exposed yet?


This is cvs as of oct. 27
Comment 1 Sven Neumann 2002-11-04 09:57:55 UTC
Double-click a palette in the Palettes list to open the Palette
editor. Pick a color from the palette preview. Is that what you are
missing?
Comment 2 Jim Meier 2002-11-04 10:30:16 UTC
Yes, that works.

What is confusing to me is that once I select a palette in the
<images>->palettes dialog, it is not clear what I must do to choose
colors from that palette. It did not occur to me to try selecting
colors in the Palette Editor dialog.

My suggestion for how I might expect it to work is:
a) the palette editor window be renamed to simply "palette"
b) the dialogs->palettes command bring up this dialog
c) a 'select' button would be used from there to open the "palette
list' dialog.

Does that make sense?
Comment 3 Jim Meier 2002-11-07 10:58:30 UTC
Actually, that won't work. Changing the selected palette does not
change the palette displayed in the palette editor window. This means
that to change palettes, I need to 

select the palette
double click it or click the edit button
delete the old palette editor dock
drag the new palette editor dock to where i had the old one set up

I'm sure this is not a common thing for the average user to do, but I
like switching among my flesh tones and other colors.

Would it make sense to simply have a "palette" dock that tracks the
currently selected palette? Of course you wouldn't want all the
palette editors tracking the selected palette.
Comment 4 Alan Horkan 2003-07-23 18:39:38 UTC
Changes at the request of Dave Neary on the developer mailing list.  
I am changing many of the bugzilla reports that have not specified a target
milestone to Future milestone.  Hope that is acceptable.  
Comment 5 david gowers 2004-03-26 03:02:05 UTC
what are you doing to break the normal behaviour?

i can doubleclick on a palette, and it shows up in the palette editor. it
doesn't create a new palette-editor dock.

i have the palette-editor docked to the toolbox, and the palette-list docked to
the toolbox. what is your docking setup? maybe this problem only occurs with
particular arrangements of docks.
Comment 6 Pedro Gimeno 2004-03-27 00:06:40 UTC
Or maybe this happened back in 2002... :)

The current behaviour seems to work quite acceptably. Can this bug be closed?
Comment 7 Sven Neumann 2004-03-28 12:13:02 UTC
IMO there's still room for improvement when it comes to handling Palettes.
Comment 8 Sven Neumann 2005-03-05 11:53:08 UTC
Since this report doesn't have make any specific suggestions on how to improve
the palette UI, and since the main problem seems to have been fixed, I will
close it as FIXED now.
Comment 9 bugzilla 2005-05-08 06:02:11 UTC
It is still not very intuitive that you must _edit_ a palette in order to 
_use_ it. What about the suggestions in Comment #2? They sound very reasonable 
to me.
Comment 10 Michael Schumacher 2005-05-10 08:26:12 UTC
A patch will make it more likely that this is considered for future GIMP versions...
Comment 11 weskaggs 2006-06-16 16:50:29 UTC
Revising summary to reflect the remaining issue, and upgrading target from Future to 2.6.
Comment 12 Roman Frołow 2006-07-09 22:59:37 UTC
I think solution from bug #346884 should solve this problem
Comment 13 Sven Neumann 2006-08-07 14:44:13 UTC
Let's close this one as a duplicate of bug #346884 then.

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