Project

General

Profile

Bug #12558

Strange behavior of the "chromatic aberrations" module

Added by Jannis V 11 months ago. Updated 9 months ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
Darkroom
Target version:
-
Start date:
01/20/2019
Due date:
% Done:

0%

Estimated time:
Affected Version:
git stable branch
System:
Ubuntu
bitness:
64-bit
hardware architecture:
amd64/x86

Description

After updating to the 2.6.0 release, the "chromatic aberrations" module seems to be broken.

Steps to reproduce

  • Open an image in the darkroom.
  • Enable the "chromatic aberrations" module
  • Switch to an image which does not have "chromatic aberrations" enabled using the film strip in darkroom
  • Switch back to the image where "chromatic aberrations" was enabled

Behavior

  • "chromatic aberrations" shows up in the history stack of the image where the module was enabled
  • The "chromatic aberrations" module is shown as "switched off" in the corrections group for this image
  • The other image shows the "chromatic aberrations" module as "switched on", but it does not show up in the history stack

Expected Behavior (before 2.6.0)

  • "chromatic aberrations" shows up in the history stack of the image where the module was enabled
  • The "chromatic aberrations" module is shown as "switched on" in the corrections group for this image
  • The other image shows the "chromatic aberrations" module as "switched off" and it does not show up in the history stack

History

#1 Updated by Jannis V 10 months ago

Additional information: The behavior also occurs with the latest 2.6.0 download for Windows.

#2 Updated by Jannis V 9 months ago

The problem does not occur anymore with darktable 2.6.1.

Thanks for the fix!

Also available in: Atom PDF

Go to top