https://bugs.kde.org/show_bug.cgi?id=421977

--- Comment #2 from hawaiiga...@hotmail.com ---
(In reply to Ahab Greybeard from comment #1)
> Can you try this with the 4.3.0 beta-1 (which is very close to formal
> release) to see if any of these problems are taken care of?
> 
> You can get it from here:
> https://krita.org/en/item/first-beta-of-krita-4-3-0-released/# and you can
> use the portable .zip version if you prefer.
> 
> There are two points in your post that puzzle me:
> 
> "the shapes in "MASK_a" and MASK_b" only appear when their layers are made
> visible."
> "Vector shapes that were in hidden layers can reappear if the layer is
> turned back to visible, correcting the previews in the process."
> 
> Isn't that to be expected? If a layer is invisible/hidden, it won't be seen
> or affect anything.

I tested the 4.3.0 version you linked to, and that seems to have indeed taken
care of the problem. I loaded the file several times, restarted Krita a few
times in-between as well, but the file came up properly every time. Other files
that had similar issues did as well.
I don't want to call it an unanimous "solved" since the issue occurred somewhat
randomly, but it seems to work for now.

My apologies about the puzzling points, I missed out on some crucial
information there. What I meant is that the previews in the "Layers" window
were empty as well. 
E.g., "MASK_a" should have shown the bright green shape in the preview, even
when the layer was checked as "hidden". But the preview in the "Layers" list
only showed an alpha-grid square - as if the layer was empty.

So, what I meant to say is that the preview only updated correctly once a
hidden layer was turned back to visible. 
The reason I didn't specify this is because I was more focused on the general
symptom of Krita behaving as if all vector layers were empty, and depending on
the state of each layer, I needed different kinds of "triggers" to make the
vector shapes visible again. In the case of a layer that was hidden when I
saved the file, un-hiding it was that trigger.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to