It is a bug, one going back to CM2, and Ive fixed it for the next release. The shadow value was always RGB(0,0,0). Highlights work as they should.
IIUC, the shadow target values were not being read; rather, RGB (0,0,0) was always being used regardless of what the user inputed for the shadow target values. Correct?
Another change: I think the shadow values used for the threshold display image should always reflect the last S/H pins that were used, defaulting to the target shadow/highlight values in the config dialog. This is the behavior from CM2
IIUC, you are saying that the last used values for the s/h pins will be used for every image regardless of the user inputed values. If this is so, why have user inputed default values? I would expect an application to always use my defaults, save for those images where I want to make an exception. It would drive me batty to have worked on
one high/low key image, have modified the s/h pin values, and then start to work on other images and have to reset the s/h pin values
again.