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 325799 - Brightness/Contrast UI improvement suggestion
Brightness/Contrast UI improvement suggestion
Status: RESOLVED DUPLICATE of bug 165330
Product: GIMP
Classification: Other
Component: User Interface
git master
Other All
: Normal enhancement
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-01-04 21:22 UTC by Luke Hutchison
Modified: 2006-01-05 02:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Luke Hutchison 2006-01-04 21:22:22 UTC
I just saw a great feature in the UI for some MRI software.  In
Brightness/Contrast adjust mode, the user was able to click and drag anywhere on
the image, and left/right was mapped to brightness, while up/down was mapped to
contrast.  It made it very easy for the user to explore the 2D parameter space,
and simultaneously find optimal values for both parameters.

It is possible that other 2D quantities in the GIMP could be adjusted in similar
ways, or 3/4D quantities could be adjusted by holding down Shift/Ctrl.  e.g. in
the HLS adjustment mode, the user could adjust lightness and saturation by
dragging, and hue by shift-dragging.

As it is, the drag operation is not used by any of these modes as far as I can
tell, clicking just pops up the dialog to adjust Brightness/Contrast etc.
Comment 1 Michael Schumacher 2006-01-05 01:12:42 UTC
Drag is used by the brightness/contrast tool.
Comment 2 Luke Hutchison 2006-01-05 01:29:47 UTC
You can drag the sliders but you can't drag on the canvas.  At least not with gimp-2.2.9.  I just tried it.
Comment 3 Michael Schumacher 2006-01-05 02:04:35 UTC
You filed this bug for current CVS, and dragging is available there. If there is something that should be changed in its behaviour, please file a new bug for it.

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