https://bugs.kde.org/show_bug.cgi?id=399152

            Bug ID: 399152
           Summary: [feature request] create new layers above the selected
                    group
           Product: krita
           Version: 4.1.1
          Platform: MS Windows
                OS: MS Windows
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Usability
          Assignee: krita-bugs-n...@kde.org
          Reporter: katearche...@yandex.ru
  Target Milestone: ---

When creating new layer with the selected group the layer is created inside the
group, i.e. one level down.

how to reproduce:
1. Create a group.
2. Select it.
3. Create a new layer(via hotkey or a button at the bottom of the layer
docker).
4. The layer is created inside the group, one level down from the selected
position in the layer stack.

Expected: As with the creation of the layers with a layer already selected in
the layer docker, I expect it to create a layer above the group layer, not
inside/under. 

This is bothering me for three reasons: 

First is inconsistency, since creation of the layer with a layer selected works
in one way(creates a layer on the same hierarchy level as firstly selected and
placed above it) and creation of the layer with a group selected works in other
way(creates a layer one hierarchy level down inside the group under the
selected position in the layer docker). 

The second is that it can be pretty frustrating to pull that created layer back
to the top hierarchy level if there are no individual layers there since the
gaps between groups are too small and seven times of ten tries you'll drop that
layer not between groups but inside of them. 

The third one is it's an extra action where it shouldn't be. If I want to
create a layer inside a group I choose a layer inside a group and I'll be fine.
If I want to create a layer on the same level of hierarchy I'll choose the
element on the same level and I'll be fine. But with this behaviour I spent one
extra action to get where I want to for now reason, since the only use case I
can imagine this behaviour is make sense when you have an empty group and that
is in my opinion is far more rare situation than a creation of the layer
without wanting it to go under, not above the selected element of the layer
stack.

I know that it's kinda debatable but nonetheless kinda bothering me every time
when I fight with the layer docker over trying to place the layer where I want
in to be(Both in terms of logic of the placement and not-so-refined margins of
the drop-zones).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to