I'm not sure if this is a bug or if there's something I'm missing here, but I'm having trouble manually painting in a transparency mask, specifically, while the mask layer is isolated. The brush strokes either don't show at all while painting, or they show show in a very random way. However, when exiting the isolated layer mode, I can see that the brush had been working the whole time. Then, when I isolate the mask layer again, the brush strokes are correctly shown. I'm on ubuntu 18.04 and have so far been able to reproduce this problem both on the version in the default ubuntu repos, but also the latest version (4.1.5), installed manually as an appimage. Is this a bug, or am I missing something? Thanks.

I've not used Isolate Layer before and it does behave as you describe in the 4.2.0 pre-alpha (19ba224) appimage version. It seems to be a bug and a developer comment would be useful. You could raise a bug report anyway.

As a workaround, you could Convert the mask to a Paint Layer to do work in it that is clearly visible, then Convert it back to a Trasparency Mask if you need to.

Apparently, this bug was reported and confirmed back in April: https://bugs.kde.org/show_bug.cgi?id=393455
I guess we'll just have to wait for a fix. Who knows how long it will take.

That is, indeed, impossible to say. I think nobody really grasps how understaffed open source projects tend to be, or how crazy it is that we actually manage to make something that people can use with how few people actually work on the code.

Sorry if I came off insensitive. Keep up the good work.

Nah, this was just me being slightly desperate at times

@boudewijn

The good news is that you have a small army of dedicated testers who don't let anything slip by them and have no hesitation in telling you what needs fixing We don't say it enough but we are grateful and appreciative of all the work that the krita developers do. Thank You!

And I'm really grateful for the testing .

Btw... I fixed a twelve-year old issue today, so if people could test the nightly builds tomorrow... The issue was this: https://bugs.kde.org/show_bug.cgi?id=365222 -- and the fix might've broken anything that's to do with shortcuts...