Editing should not affect hidden layers

[cri5ti]

Editing should not affect hidden layers, but if you just changed the current frame by clicking on a new frame, edits will affect hidden layers, which is counter intuitive, and you usually don't notice until much later.

• Aseprite version: v1.2.17-x64 (tried in v1.2.19.2-x64)
• System: Windows

[sumibi-yakitori]

I don't see a particular problem with this, as I can simply lock the layers. The current aseprite behavior is necessary for me.

[hiddenhare]

Reproduced this in Aseprite 1.2.25-x64, Windows 10. I agree that it feels like a UX bug.

• The behaviour is inconsistent before and after changing frames with a selection active. (Before, only selected layers are edited when moving or deleting a selection; after, all layers are edited.)

• The behaviour is also inconsistent with locked layers. As far as I can tell, there's no way to move the content of a locked layer.

• The behaviour is inconsistent with all other tools (including the Move tool), which will refuse to operate when only hidden layers are selected.

• The consequences for accidental editing of hidden content can be severe. In the worst case, the user might accidentally delete or ruin several layers, and then save their work.

[thomasgoldstein]

I'm seeing a quite unsettling behavior which is most likely linked to the one described here, so I'm sharing this here instead of creating a new issue. It's not just that you can edit hidden layers, it's also the fact moving a selection on a hidden layer results is completely deleting the whole selection, somehow.

Example:

• Have a layer which contains graphics
• Hide that layer
• Create a big selection on that hidden layer (in a place where the graphics should be), then move that selection to any direction by 1px
• Show the layer again

Result: everything you selected and moved has completely disappeared. That is to say it does not behave as it would if the layer was visible the whole time.

[dacap]

I thought this bug was fixed, but it looks like it's still present when the active layer is the hidden one. Thanks for reporting @thomasgoldstein