Bug 454960

I cannot reproduce this.

Created attachment 149525 [details]
Left: before saving multiple selections without a parent layer. Right: after re-loading the save of the left

Left: before saving multiple selections without a parent layer. Right: after re-loading the save of the left

My bad, the conditions upon which it appears are when multiple local selection layers are present and NOT parented to any layer. Not all of them are saved, and for some reason one is always placed on the top of the layer stack when the save is re-loaded?

But how have you actually managed to create local selection masks that are not parented by a layer? If I try that, the mask becomes the global selection again.

I drag all the local selection layers to the bottom of the layer stack. I thought this was standard functionality?

No... selection masks are masks, not layers, and they are always supposed to be attached to a layer. Actually being able to do this is a bug in itself.

Despite it being a bug, I've actually found this very useful, as having parentless selection masks allows them to be activated while selecting any layer OR another mask. I'm using this 'functionality' to paint on a transparency mask with a local selection active (which I can't do if the local selection is parented to anything, even including the layer the mask belongs to.)

If no Global Selection Mask is active, a Local Selection Mask can be dragged to the bottom or top of the layer stack to become a Global Selection Mask.
You can have a large number of Global Selection Masks but only one of them can be active.
Similarly, you can have a large number of Local Selection Masks on a paint layer but only one of them can be active.
You can drag a Global Selection Mask onto a paint layer where it will become a Local Selection Mask.

If you Save then only one Global Selection Mask is preserved but all Local Selection Masks are saved.

I store Selection Masks as Local Selection Masks attached to a 'storage layer' to preserve them.

It would be useful if multiple Global Selection Masks could be saved and restored.

Aha, so that's what this is called. Yes, what I seem to have reported as a bug is in fact that GLOBAL selection masks aren't all saved with the file.

I'll Confirm this for the 5.0.6 and the Jun 10 5.1.0-prealpha (git ab9510e8c9) appimages on Debian 10.

Multiple Global Selection Masks can be created and exist in a stable and useful way in the Layers docker.

However, after Saving, only one Global Selection Mask is preserved in the .kra file.

A workaround for this is to drag the Global Selection Masks onto a 'storage layer' so that they are converted to Local Selection Masks, which are preserved in the .kra file after Saving.

Git commit 7f226b9e9c41f1e3520a28f1a52bcaa75b6947d3 by Dmitry Kazakov.
Committed on 22/06/2022 at 12:47.
Pushed by dkazakov into branch 'master'.

Fix lost masks when opening a document with two root inactive selection masks

M  +1    -1    libs/image/kis_group_layer.cc
M  +15   -2    plugins/impex/libkra/kis_kra_loader.cpp

https://invent.kde.org/graphics/krita/commit/7f226b9e9c41f1e3520a28f1a52bcaa75b6947d3

Git commit c44cc4efc13256da2bfd5d3fa74a728097fb9def by Dmitry Kazakov.
Committed on 22/06/2022 at 12:48.
Pushed by dkazakov into branch 'krita/5.1'.

Fix lost masks when opening a document with two root inactive selection masks

M  +1    -1    libs/image/kis_group_layer.cc
M  +15   -2    plugins/impex/libkra/kis_kra_loader.cpp

https://invent.kde.org/graphics/krita/commit/c44cc4efc13256da2bfd5d3fa74a728097fb9def