https://bugs.kde.org/show_bug.cgi?id=399152
--- Comment #2 from katearche...@yandex.ru --- (In reply to Boudewijn Rempt from comment #1) > Um... Creating the layer inside the group when the group is selected is > consistent with other applications like Gimp and Photoshop. It also provides > for a common workflow (create a group, populate it with layers). But we've > been getting patches and wishes for this for some time now, so I'm > wondering: what is making people ask for this right now? > > See https://bugs.kde.org/show_bug.cgi?id=399103 and > https://phabricator.kde.org/D15523 > > *** This bug has been marked as a duplicate of bug 399103 *** Well, in my experience its a combination of two things: Different expected behaviour for seemingly the same elements in terms of logic and, more importantly -- the kinda cumbersome drag'n'drop behaviour: it has very small gaps between the layers/groups on the same level(i.e. you have to be veeery careful when trying to drag and drop the layer to the new position in the stack) and laggy feeling when after you have missed and drop a layer in the wrong group krita starts to refresh the preview/structure of the image and on large files(like 50+ layers 7k+ size) it's very noticeable and a little disruptive. I've just tried to drag'n'drop im phiotoshop and yes, it has much more large margins for drag'n'drop and a task of placing a layer anywhere in the stack where you want it to be is totally no-brainer. Nut in krita if you have groups placed one next to each other it's like a minefield :( So an easy fix for this that comes to mind first is to synchronize the logic between the layer-on-layer and layer-on-group behaviour and so I suspect each of the people who report it is thinking about it. But of course the more fluid drop zones will make that minefield-trip much more tolerable too :) -- You are receiving this mail because: You are watching all bug changes.
