https://bugs.kde.org/show_bug.cgi?id=343115
Tyson Tan <tyson...@tysontan.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|RESOLVED |REOPENED
CC| |tyson...@tysontan.com
Resolution|FIXED |---
--- Comment #5 from Tyson Tan <tyson...@tysontan.com> ---
This bug still exists in 4.3.0/5.0.0pre-alpha.
There are a series of related bugs I’ve discovered when doing community
support:
Krita won’t save imported Photoshop .act palette. It will drop any imported
.act palette upon re-launch.
Krita will break an imported Photoshop .act palette upon re-launch if it was
embedded in a .kra file. The said palette is kept, but completely glitched out.
When importing a palette, Krita will ask “Do you want to store this palette in
your current image?”, if you choose “No”, Krita won’t import the palette, but
loads “Swtch CMYK” palette.
When importing a palette, Krita will ask “Do you want to store this palette in
your current image?”, no matter which you choose, Krita will always set the
value as “Document” in Palette docker’s “Folder” icon (Edit this Palette)
dialogue.
Workaround for importing Photoshop .act palette in Krita:
Import a .act palette
Store in current image - Yes
Export the imported palette as .kpl
Load the .kpl palette
Re-launch and it’s still there.
--
You are receiving this mail because:
You are watching all bug changes.
