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 136861 - Enhance color picker to set multiple color reference points
Enhance color picker to set multiple color reference points
Status: RESOLVED DUPLICATE of bug 137776
Product: GIMP
Classification: Other
Component: Tools
1.x
Other All
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2004-03-11 06:18 UTC by Tim Jedlicka
Modified: 2004-03-22 14:25 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Attachments
mockup of color picker reference points (70.21 KB, image/jpeg)
2004-03-11 06:22 UTC, Tim Jedlicka
Details

Description Tim Jedlicka 2004-03-11 06:18:46 UTC
When doing color correction or trying to apply the zone system and adjust
exposure latitude it is handy to be able to set several reference points.
The color picker tool could be enhanced to allow you to set a reference or
anchor point. The point should be numbered and the values for the point
displayed - either on the image itself (perhaps with a transparent
background) or in a seperate docked window or with a float-over popup. The
reference point should have the ability to "snap-to-point" so if you find a
good middle grey for example, you can easily apply the
Levels-Grey-Eyedropper to the previously referenced point. Using the color
picker and adding the XY coordinates would be useful (ala Info-Window).
Showing the before and after pixel values would also be useful - imagine a
color-blind person being able to do color correction based on the pixel values.
Comment 1 Tim Jedlicka 2004-03-11 06:22:14 UTC
Created attachment 25507 [details]
mockup of color picker reference points
Comment 2 Michael Natterer 2004-03-22 14:25:56 UTC
Closing this bug as duplicate of the newer bug #137776 because
#137776 has a more detailed discussion and the suggestion
to do this using a sepatate tool seems more feasible and sane.


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