Bug 441096

Summary: Color selector doesn't intuitively update when selecting a different color model type in Color Selector Settings
Product: [Applications] krita Reporter: tomtomtomreportingin
Component: Color SelectorsAssignee: Krita Bugs <krita-bugs-null>
Status: CONFIRMED ---    
Severity: normal CC: 1012468643, halla
Priority: NOR    
Version First Reported In: 5.2.9   
Target Milestone: ---   
Platform: Appimage   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description tomtomtomreportingin 2021-08-17 20:53:32 UTC
SUMMARY
Something I recall confusing me a fair bit when first getting into Krita was configuration of the Color Selector. When choosing a different Color Model Type, the Color Selector doesn't automatically conform to an equivalent form of that Color Model, until the user explicitly selects one.

STEPS TO REPRODUCE
1. Configure Krita -> Color Selector Settings
2. For demonstration, with HSV selected, select the common square selector with hue ring border (bottom side is black).
3. Select a different Color Model type, for example HSL.

OBSERVED RESULT
The color selector stays the exact same despite selecting a different color model type. The user must realize that they have to explicitly set a new color selector for one that conforms to the selected color model.

EXPECTED RESULT
The color selector should automatically conform to the closest color model equivalent as soon as a new color model type is selected.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian sid
KDE Plasma Version: 5.20.5
KDE Frameworks Version: 5.78.0
Qt Version: 5.12.9 (Appimage)

ADDITIONAL INFORMATION
HSV color model has 9 different color selectors while other color models have 7 different color selectors. HSV has two extra color selectors for alternative "spectrums" of existing forms.
Comment 1 Lynx3d 2022-07-09 03:52:56 UTC
*** Bug 456496 has been marked as a duplicate of this bug. ***
Comment 2 Vitamorus 2025-05-01 11:07:46 UTC
The more recent Wide Gamut Colour Selector is an upgrade to the Advanced Colour Selector and doesn't have this problem, so the solution is to simply switch to the former. 

But I'm gonna move this ahead to 5.2.9 even though I'm not sure it's going to be looked into. I remember asking in the IRC previously whether to dismiss bug reports for the Advanced Colour Selector or not, since the Wide Gamut selector replaces it. The consensus seemed to be "probably not yet".