SUMMARY After testing with the Jan 05 4.4.3 (git 79dcac7) appimage The Palette Docker UI/UX bug: https://bugs.kde.org/show_bug.cgi?id=431220 has been Resolved-Fixed by adding the RGBA values of the palette swatch to the tooltip display. This reveals that the palette stores and uses alpha. This alpha value is not returned/used when a swatch is selcted as a colour. DESCRIPTION If a canvas colour with alpha less than 1 is picked and added to a palette, the resulting swatch has the RGB and A values stored in it and also displays the appearance of the colour with low alpha i.e as it was on the canvas. If the swatch is then clicked to select that swatch colour for use, the Opacity slider on the Toolbar renains at whatever value it was and is not set according to the swatch alpha value. The Opacity slider on the Toolbar should be set according to the selected swatch alpha value.
This really needs a bit of debate, and perhaps be made into an option, because I can imagine that people will find it very annoying that the opacity changes when selecting a color.
> The Opacity slider on the Toolbar should be set according to the selected swatch alpha value. I never used any software with a palette doing this behavior. Why I would like my 100% opacity brush to load a color that reset my slider to 50% opacity because it has a 50% alpha stored? I'm not sure I can imagine any workflow/usecase to justify that feature but I'm open to read your examples and change my mind.
I'm working on a discussion topic for the krita-artists.org website.
I didn't examine this deeply enough. The picked colour alpha is stored in the palette structure internally in krita but is not saved in the resources folder or in the document palette (if that option is chosen). Setting to Resolved - Not A Bug