https://bugs.kde.org/show_bug.cgi?id=466648

            Bug ID: 466648
           Summary: Color management issue - docker overview on second
                    display
    Classification: Applications
           Product: krita
           Version: 5.1.5
          Platform: Microsoft Windows
                OS: Microsoft Windows
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Color models
          Assignee: krita-bugs-n...@kde.org
          Reporter: i...@cgidesign.de
  Target Milestone: ---

Created attachment 156862
  --> https://bugs.kde.org/attachment.cgi?id=156862&action=edit
Krita overview docker - wrong color management - no icc profile switch

SUMMARY
Krita (overview docker): ICC profile of display2 is used for display1. Wrong
color management.


STEPS TO REPRODUCE
1. in Krita's settings assign ICC profiles to display1 and display2. Use
Krita's krita25_lcms-builtin-sRGB_g100-truegamma.icc for display1. This profile
is intentionally wrong - it is used to trigger an obvious change of the image
representation when this profile is used. Use a "correct" ICC profile for
display2 (e.g. one created with a probe or a default sRGB profile). Set
rendering intend to relative colorimetric.
2. Restart Krita on display2
3. Open the docker overview and move it to display1
4. Because display1 uses the "wrong" linear profile, the image should get much
darker. But it does not.

OBSERVED RESULT
The overview docker does not trigger an ICC profile switch when moved to a
different display.

EXPECTED RESULT
The overview docker triggers an ICC profile switch when moved to a different
display.

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Please see attached images for explanation.

Intention for bug report:
I paint on the pen display2. For color critical work I like to see a cloned
view of the document on my reference display1 (reason: most pen displays can't
be calibrated accurately).
The clone view should use the icc profile of display2 to show "correct colors".

A more general request would be, that all UI elements which "show or manipulate
colors" should know on which display they are and switch ICC profiles
accordingly (e.g. moving the color selector as a floting docker to display1
should also trigger an ICC profile switch).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to