New Componets are not added/subtracted/intersected above the currently selected Component.

[C.Cella]

These are the steps to reproduce the issue

1. Open en a photo and create a Mask with 3 component.
2. Select the component at the very bottom of the list.
3. Subtract/Intersect/add a new component to the existing Mask.

Result: As of now the newly added/subtracted/intersected component is placed on top of all existing components in the Mask.

EXPLANATION:

Always putting a new component on top of all existing ones, in chronological order, is not the best solution at all!

Components are not like Masks, the order of components is important, it matters!

• The default behaviour should be to put a new component above the currently selected one.
• Alternatively we should have at least the option to set "Always create new component above currently selected one" as the default behaviour when creating new components.

• In both cases above if no component is currently selected, so if the Mask is selected, the newly added component is put above all existing.

[C.Cella]

I apologize for the typos and the errors.

I was about to correct them but I pressed "post" inadvertently.

[Rikk Flohr: Photography]

This is not a bug. The behavior is as-designed. New components will always be added to the top of a mask's component list. 

You can, of course submit a feature request to make a change to existing behavior. 

[richardplondon]

And: if the default "add on top" position is ever not what you want, mask "layers" can be dragged into some other functional stack order.

IOW to get the desired dependencies, LrC does not require you to have created them in that working order.

That said, IMO it IS the sensible default assumption, that new mask elements will tend to be an "override" responding to whatever was already happening, however achieved. And that tends to presume: applied on top.

[C.Cella]

@richardplondon

It should be sensible to assume that users know that components' order matters.

Here is a hypothetical Mask structure.

Masks 1

Exposure + 0.5 

Linear 1

Radial 2

Brush 6

Radial 1

Brush 4

Brush 3

Brush 2

Brush 1

If the user wants to create a new component or do an intersection/subtraction on top of everything else then it would simply: select top component > new component.

Or: deselect current selected component > create new.

If a users wants to intersect an Ai Selection and affect only Brush 1 (which is a perfectly intelligent and actually smart workflow) it should:  select Brush 1 and create new.

This second workflow is not possible now.

Now we: create new > drag to desired position.

First select Component > then create new (knowing it will be above the currently selected)

This is the best workflow!

This is what countless of us has been doing with Layers in Photoshop for years and years.

 .

[C.Cella]

@Rikk Flohr: Photography 

I understand it's not a bug but it's nonetheless a questionable design choice.

Components' order matters so it's not wise to just "add above everything else" by default.

In Photoshop the Layers' order matters as well and, in fact, a new Layer is added above the currently selected Layer!

Adding above selected "item" is the expected and established behaviour.

.

[C.Cella]

@Rikk Flohr: Photography 

As you suggested I submitted a Feature Requests and allow us to chose the "Create/Intersect/Subtract new Component above currently Selected Component" as the main behaviour.

.