SUMMARY If you set up the color to be fairly bright and only on the edge of saturation, you'll see that after decreasing nits a lot slider will reset the Hue to the left end (red). STEPS TO REPRODUCE 1. Set up very bright blue color. It should be already white, but you'll see on semi-transparent parts of the brush that it's still blue, you just don't see it. Also Hue in the color selector will be blue. 2. Decrease nits. You'll see that the point that shows the position of the color is slowly moved towards left side. Hue is still blue though. OBSERVED RESULT 3. When the point touches the left side (= zero "saturation"), the Hue switches to red (left-most hue). EXPECTED RESULT 3. No change of Hue. SOFTWARE/OS VERSIONS Windows: 10 Krita Version: 4.3.0-prealpha (git f5dd77b) Languages: en_US, en_US Hidpi: true Qt Version (compiled): 5.12.5 Version (loaded): 5.12.5 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.18362 Pretty Productname: Windows 10 (10.0) Product Type: windows Product Version: 10 Hardware Information GPU Acceleration: auto Memory: 16191 Mb Number of Cores: 12 Swap Location: C:/Users/Agata/AppData/Local/Temp
Hey, whenever you get back touching an HDR version of krita, can you check if this is still relevant? (And perhaps check if other HDR bugs are still relevant :D) Because I definitely remember this bug, but I am not sure it is still happening.
Setting to needsinfo
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
This is still a problem.
Ok, I guess I remember it, so let's toggle it to confirmed then...
Remove triaged keyword from CONFIRMED bugs