In our documentation of the Palette docker: https://docs.krita.org/en/reference_manual/dockers/palette_docker.html It says: Column Count The amount of columns in this palette. This counts for all entries. If you accidentally make it smaller than the amount of entries that take up columns, you can still make it bigger until the next restart of Krita. ### In reality, if you put a color to column 18, then change the palette's Column Count to 17, that color swatch on column 18 is gone forever. It's not listed in the color droplist anymore, it's not coming back after you change the palette's column count back to 18. Restarting Krita is not going to help either. So what's point of telling the user to "make it bigger until the next restart of Krita"? I'm translating this and it confused the glob out of me. I don't know whether this is intended or not. If it is intended, then it's a very dangerous feature which can easily destroy people's palettes. We should warn the user about it when incompatible new column count is detected. The documentation's "If you accidentally make it smaller..." should be changed to "WARNING: If you accidentally make it smaller...the swatches outside will be lost forever!" Tested on: krita-4.3.0-prealpha-aad2969-x86_64
BTW this happens also when changing the palette's Row Count.
Yeah, I had been wondering about it as well when this was implemented :|
Git commit 2914f5986d56202a516b76e91a1112d60b65e091 by Wolthera van Hövell tot Westerflier. Committed on 07/04/2021 at 15:44. Pushed by woltherav into branch 'master'. Move otherwise deleted swatches to their own row when resizing the palette. This still doesn't solve the problem of rows resizing, but solving that will require the whole code to be rewritten from scratch because the code in question is fundamentally not designed for this. M +24 -0 libs/pigment/resources/KisSwatchGroup.cpp https://invent.kde.org/graphics/krita/commit/2914f5986d56202a516b76e91a1112d60b65e091