Created attachment 123143 [details] recording SUMMARY git 6310d2d Title says it all. When you place any layer *right below* the 'group layer', it doesn't go inside the group. It goes outside the group. I'm sorry if that's intentional. SOFTWARE/OS VERSIONS Windows: Win7 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
There are two distinct but barely separated positions which are outside-below the group or inside-top of the group. This is useful but unless you pay attention, remember the difference and move carefully it can be confusing. It would be nice if they could be more distinct, maybe by being more physically separated or maybe by the outside-below position having a different highlight colour, or both.
Logically, for this particular position(right below the group category layer), I think it shouldn't be separated. (But the dicision is yours...)
Logically, I can think of two situations where it's useful to have these two different actions. However, this will be a decision for the all powerful developers and nothing to do with me.
(In reply to Ahab Greybeard from comment #3) > Logically, I can think of two situations where it's useful to have these two > different actions. Mind if I ask what it might be? I do think it's good to have separation at below the whole group. So that we can decide whether we put the layer inside or outside. But when we put the layer right below the top 'group category layer', it should always go inside the group, I think.
Created attachment 123159 [details] Example of a large expanded group If you consider an expanded group with many layers/subgroups in it. a) If you want to move Some Layer from above the Standard Greenery Library Group to below it, you can do that with a short distance drag onto the 'outside-below' position. b) If you want a copy (or original) of bush-C.png to be placed outside and below the group, you can do that with a short movement to the 'outside-below' position on the group layer.
Created attachment 133980 [details] Recording of two different behaviours in the space between group layer and the first child layer When I was testing, it turned out that there are in fact two ways of putting the layer visibly underneath the group layer but in fact in those two positions you mentioned. In one case, there was an underline below the whole group layer entry; and in the other case, it started indented (where the child layers would start). However I also noticed that the second case is barely visible and that the exact same result can be achieved by just pointing the layer *at* the group layer (which highlights the whloe group layer rectangle, not just a line below it). Maybe it would be a good idea to just remove this possibility and rely on the "put on the group layer => put inside, on top of other child layers" behaviour?
Recently this has been giving me so much headaches since I started to work more with group layers. All I want to do is just to drag a layer into a group layer at its top position, and I have to do precision gymnastics every time to make sure it doesn't go outside the group.
Any news on this one? ;-; Aggh it's so painful to deal with this on a constant basis now that I'm using so many group layers... I'm not sure how complicated it is on the code level, but from a user's perspective it simply doesn't have to change it's position from where you put it. If you put a layer between layers, it can just stay there. *The only exception would be putting it at the bottom end inside a group where you need a little room to decide whether it should go inside or outside the group. But there's no need to have that mechanic for anything else imo.
Praying every day for this to be fixed. I still cannot understand that why it should behave this way. There's absolutely no reason to have 2 different actions at the top position inside the group. (There should be 2 actions at the bottom to determine whether it should go inside or outside the group, but not at the top.)