Project

General

Profile

Feature #8944

Increase Mouse Wheel Increments for Exposure

Added by Rick Gabriel over 7 years ago. Updated about 5 years ago.

Status:
Fixed
Priority:
Low
Assignee:
-
Category:
Darkroom
Target version:
-
Start date:
09/23/2012
Due date:
% Done:

100%

Estimated time:
Affected Version:
git development version
System:
all
bitness:
64-bit
hardware architecture:
amd64/x86

Description

Currently, each mouse wheel click for exposure changes the value by 0.01. This produces very little effect and requires lots of scrolling. I suggest changing the increment to 0.1EV per mouse wheel scroll.


Related issues

Has duplicate darktable - Feature #9939: Darkroom: larger-increment hotkeyable increase/decrease actions for Exposure and White Balance temperatureDuplicate05/03/2014

History

#1 Updated by Tobias Ellinghaus over 7 years ago

  • % Done changed from 0 to 20
  • Status changed from New to Incomplete

Not sure about this, seems to also depend on the system's mouse settings. What do others think?

#2 Updated by Jan Kundrát almost 7 years ago

I'm coming from Canon's DPP and am used to its way of working. In the DPP, the slider can only be adjusted by 1/6 EV increments and between -3 and +3. I do not have opinion on the range here, but I really like the stepping.

For me, an ideal solution would be mouse increments by 1/6 EV on one mouse wheel rotation (they are currently 0.02 for me), and a finer granularity by explicitly moving the slider by mouse or keyboard. The wheel looks like a perfect tool for the initial adjustment, and 1/6 is on par with what the DPP offers.

#3 Updated by Tobias Ellinghaus over 6 years ago

  • Status changed from Incomplete to Triaged

Hmm, no reaction from fellow developers, I am setting this to Triaged, maybe someone feels inclined to check it out then. :D

#4 Updated by Roman Lebedev about 5 years ago

  • Has duplicate Feature #9939: Darkroom: larger-increment hotkeyable increase/decrease actions for Exposure and White Balance temperature added

#5 Updated by Roman Lebedev about 5 years ago

  • bitness set to 64-bit
  • System set to all
  • Affected Version set to git development version
  • % Done changed from 20 to 100
  • Status changed from Triaged to Fixed

We do not want this to be implemented in the core.
Once Lua can deal with IOPs, it will certainly be Lua territory.

Also available in: Atom PDF

Go to top