Vlasta
yesterday
0
You can check what version you have in the main menu Help->About RealWorld Paint
It could be that at certain times, there were problems with colors due to handling of sRGB. But it should be OK in the latest version. If not, please update the description - for example what method do you use to check out the actual color? Do you have only a single layer or more, do you have any layer styles applied to it?
Mars
yesterday
0
Hi,
I'm probably not the best with words, so I made a gif: https://imgur.com/a/FJOqUxB
Its really cool to get such a fast reply. Its 2:00 midnight in Germany and somehow I thought the whole world is currently asleep 😊
Edit: Ah, I forgot to mention:
- No layer style
- Blending mode == Normal
- My Screen (Hardware) uses default RGB888 (no 10bit or HDR). Maybe that matters
- Windows 11 (10.0.26100)
Vlasta
about 22 hours ago
0
OK, thanks for the video, you have actually found a bug in the Dropper tool. It was not properly updated and reports wrong colors, the pixels in your image are in fact correct.
I will fix it, but for now, there are workarounds. Many of the drawing tools (including the Flood fill) can act as a dropper tool when you hold CTRL key and click a pixel. This method should work fine and give you back the right color. This is what I use and that is the reason I forgot to update the dropper tool. Also, the small dropper button in the color selection box should work, but this one works slightly differently - it actually takes the color from the Windows screen (so, no alpha channel), while the Dropper tool and CTRL+normal tool take the color from the raw pixels of the raster layer.
The problem was caused by an update, older version of RWPaint approximated the sRGB color space with a 2.2 power curve and the new version user proper sRGB mapping. The difference in those 2 methods is what caused the discrepancy.
(and I was actually feeding a baby, so I was awake at that time)