Bug 396779 - Desaturated reference images still give original saturated color when using the color picker
Summary: Desaturated reference images still give original saturated color when using t...
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Tools/Reference Images (other bugs)
Version First Reported In: 4.1.1
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2018-07-23 05:08 UTC by Altguard
Modified: 2018-09-28 19:59 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Video Example (2.91 MB, video/x-matroska)
2018-07-23 05:08 UTC, Altguard
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Altguard 2018-07-23 05:08:35 UTC
Created attachment 114077 [details]
Video Example

Adding a reference image, desaturating the image using the reference image tool options, then color picking from the desaturated reference image will pick the original saturated color from the reference image.

Reproducable: Always

Steps to reproduce:

1) Add a color reference image

2) Us the Reference Image Tool Options to desaturate the reference image

3) Switch to the Color Selector Tool and pick a color from the desaturated reference image

Actual Result:

The Color Picker will pick the original, fully saturated color from the reference image.

Expected Result:

The Color Picker picks the desaturated color.
Comment 1 Eoin O'Neill 2018-09-15 22:57:35 UTC
Application Version: Master Branch
RESOLVED > WORKS FOR ME
System Info:
Ubuntu 18.04 bionic

I was unable to reproduce this bug in the current master branch of Krita. All range of desaturated values will properly be sampled with color picker. Try a nightly to see if this is still giving you issues. Also, perhaps consider giving more details about the filetype and whether your settings designate embedding image into krita.
Comment 2 Altguard 2018-09-28 19:59:24 UTC
This escaped my mind until the 4.1.3 release - the issue was noted as fixed in the patch notes and, sure enough, it seems to have been resolved with the latest version.

I apologize for not providing more information before.