Bug 399144

Summary:	Transparency mask doesn't work with pass-through groups
Product:	[Applications] krita	Reporter:	katearcher89
Component:	Usability	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist	CC:	halla, tamtamy.tymona
Priority:	NOR
Version First Reported In:	4.1.1
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description katearcher89 2018-09-27 13:30:51 UTC

Although groups have visibility slider and can have different blend modes etc it's not possible to use pass-through mode AND transparency masks to mask out some parts of the group's resulted image.

From my understanding there is nothing preventing such use case on a technical level since the opacity of the group can be changed already and it's possible to add transparency masks to the layers with blend modes other than normal as well.

It's really complicating things since it's impossible to group layers in a logical way(i.e. all color tweaks combined in one place etc) and as a result the root level turns into a mess after a while.

I know it's been reported already more than a year ago but since the is the bugsquashing crowdfunding focused on papercuts(as it can be seen through preliminary polls) I've decided to re-report it again since this papercut is totally making things much more cumbersome that it should be.

Comment 1 Halla Rempt 2018-09-27 13:49:31 UTC

Um... If there's already a report for this in bugs.kde.org, we probably should close this bug as a duplicate? Having two reports doesn't help :-)

Comment 2 katearcher89 2018-09-27 14:17:52 UTC

(In reply to Boudewijn Rempt from comment #1)
> Um... If there's already a report for this in bugs.kde.org, we probably
> should close this bug as a duplicate? Having two reports doesn't help :-)

Formally -- yes :)

But since things haven't moved forward for a year I've decided to draw some attention to this problem since it's really annoys me and now is such an opportunity to get it fixed during the bugsquashing campaign.

Comment 3 Halla Rempt 2018-09-27 14:32:03 UTC

Well, we could close the other report then as a duplicate of this one. But I really cannot promise quick service :-)

Comment 4 katearcher89 2018-09-27 14:48:11 UTC

(In reply to Boudewijn Rempt from comment #3)
> Well, we could close the other report then as a duplicate of this one. But I
> really cannot promise quick service :-)

Looks fine to me :)

Comment 5 Tiar 2020-04-01 16:36:21 UTC

I marked this as a duplicate of the other one because the other one had more votes.

*** This bug has been marked as a duplicate of bug 381287 ***