https://bugs.kde.org/show_bug.cgi?id=398990
--- Comment #27 from katearche...@yandex.ru --- (In reply to Raghavendra kamath from comment #26) > Hi Kate, > > Thank you very much for the images, that makes it clear to understand what > you want. > > From what I understand you want the filter to only applied to the selected > layer and merged down, disregarding the unselected layer, that is the filter > should not be applied to the unselected layer and it should be reverted to > how it looked without filter. > > Now as we have told you in previous comment that in krita the filter layers > are just like new "layers from visible + the filter applied to them" so we > try to keep the output as close to what users see prior to merging. > I understand what are you trying to say but it's not intuitive at all. Just for a moment wear my boots with my train of thought: I see two layers(and a bunch of other i'm not interested by), I want to merge these two layers, I select them to isolate from the others but, by some miracle, in the end I got not only the layers I've selected but all other layers merged in that I've NOT selected purposely and by intent because I was merging these two. To expand: Let's say you have two paint layers. They are displayed on a canvas exactly the same way as two layers from my latest example but merging them together won't result in the merging in layers that wasn't selected. What I grieve for is a lack of consistency: in the end filter or not it's all _layers_, they exist in a same docker etc and a user should not be bothered with all the booby traps here and there when in one case selected layers merging in one way and in the other case completely differently from the first. > In your scenarios the merged output changes from what you have prior to > merging, it might be easy to guess in simple situations like having two > three layer and some adjustment layers, but It gets tricky when you'll have > filters such as blur or when you'll have more than 10 or 20 layers in > between with different blend modes. > I understand that merging with different blend modes can lead to unexpected results as well, and that's the case for Photoshop and other layer/blending operating programs as well. But there is a great difference between cases: "selected layers merging with no additional pixels created" and "selected layers merging with all the pixels from non-selected layers merged in as well". > May I request you to also show us images what photoshop does when you have > blur as filter layer, as you had in your first attachment. I can do that but it would be of no use since photoshop' adjustment layers are indeed working somehow differently from Krita's filter layers(i'm not sure about it's inner workings). They have two adjustment layer systems in place, the legacy one, adjustment layers, and smart layers, which are more or less works as krita's filter layers. - The legacy one was there like forever and from my understanding it's designed to work as fast as possible, therefore only selected filters are available as adjustment layers. - Smart filters are applied to smart objects only and in this case the whole set of filters are available, they can be stacked, edited at any given moment turned off and on again etc. The catch is that to apply these smart filters to a set of layers you must convert them into a smart object beforehand. So in a sense photoshop' smart filters work the same way krita filter masks. Returning to the question: The blur filter is available only as a smart filter so it is attached to a smart object which itself is just one layer from a layer stack point of view. So it's already "merged" with filters applied to it in the stack and they only way to merge in with filters is to flatten a layer which is working(kinda obviously) the same way as in krita. > > The design of the filter layer in Krita is different from photoshop's > adjustment layers. And krita users are more accustomed to the behaviour that > we have now. Changing it will lead to discomfort to many of the krita users > who rely on the existing behaviour. > To be honest I'm soooo not sure that your average joe keeping in his head that merging selected layers with filter layers without grouping selected layers beforehand would lead to other results than as with grouping them and/or that the "feature" of merging in pixels that wasn't there before can be used in any workflow usefully. > Still if you feel like we need to change the behaviour I humbly suggest you > to start a discussion topic in forum, so that we can gather more support and > opinion from the artists and we will get know what they like. > > P.S. The bug title can be - [Wish bug] Make filter layer affect only the > selected layer when merging down. Yes, I do feel like this behavior is inconsistent and misleading and I'll make a topic on a forum about it later on, thanks for a meaningful discussion, sorry if I was a little too aggressive but krita is a great piece of software and this kind of papercuts(because I CAN do a merge of selected layers with "what-I-see-is-what-I-get"(I select layers so I want to make actions only with them) approach, it's already there but to do this I have to make actions that are tedious and easily automated and implementing it will make things much more uniform in terms of UX and what is expected from merging selected layers) needed to be talked over. -- You are receiving this mail because: You are watching all bug changes.
