color calibration module - improve white balance picker handling
The white balance picker of the color calibration module can lead to strange results if the user is not aware that he has set a target color different from neutral. This is well documented, but every so often people (me included) stumble over this. There is an "active" appended to the label of the "area color mapping" collapsible section if the values differ from neutral since some time now, but it can easily be overlooked.
This could be improved by a change in the color calibration GUI:
- the current picker always and only sets the white balance using neutral values
- in the "area color mapping" collapsible section, a second picker is added that, depending on "area mode", picks a color from a source image or applies the color to target images.
Of course this would be a change of the GUI and I don't know if this is wanted. But it could help avoid mistakes: a user wanting to transfer colors between images must expand the section to get hold of the picker, so he is automatically aware of this functionality and also sees the currently configured target values.
I suggested this same UI when the area color mapping feature was introduced and the original author of the functionality strongly objected (though he's left the project now). I very much support this feature request and IMO something similar should be done in the exposure module (in which case the main picker should set the exposure to 50%).
This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.
Hi, in #19838 I have faced the problem due to the area color mapping feature design. Even though I am still not sure how this feature works (even after reading the docs). I have noticed quite exceptional behaviour of the module.
Its last configuration is saved into the darktablerc file and then is applied to each new edit. The module's configuration won't reset when "module reset" is pressed—to disable (active) message. One needs to deactivate (double click) all sliders.
Even though I have noticed an active message, I initially haven't found the way to disable the submodule - to double-click all sliders.
Yes, the UX here is pretty bad. And the exposure module has the same problem.
Bruce Williams has some videos where he explains how to use this feature.