Make it possible to move a selection of multiple layers at once

It seems it’s possible to move an entire layer of multiple layers―with multiple layers selected in the layers docker―, but it’s not possible to move a specific area(of multiple layers) selected with a selection tool.

I can workaround it by using transform tool instead, but I’d like to be able to simply move the selected area of multiple layers.

This request is not understandable at all.
Could you anwser the following Questions:

  • What do you want to do exactly ?
  • Could you explain your workflow step by step?
  • What is the wanted outcome?

For example:
As a user I want to be able to select an area over multiple layers and move the selection with the “move” tool.

My workflow:

  1. Draw on layer 1,
  2. Add new layer (2),
  3. Draw on layer 2
  4. repeat step 2 and 3, 5 Times
  5. Select an area
  6. Select all Layer
  7. Use the move-tool

Expected Behaviour:

  • Only the selection is moved

Current Behaviour:

  • All selected Layers are moved

As anwser for the given example, if that is what you wanted to have:
You can put multiple layers into a group.
When you select an area you can select the group-layer in the layers-docker and use the transform-tool.
Now you can move the selection in all layer within the group

As a user, I want to be able to select an area, and select multiple layers in the layers docker, and move them with Move tool at once. In short, I want to move a selected area of multiple layers at once.

The current behavior is that the move tool cannot move the selected area of multiple layers, but either the selected area of a single layer or the entire layer data of multiple layers(without selection). Even if I put them inside a group, it still doesn’t do the job, unless I use the transform tool.

Current behavior:

Expected behavior:

It’s a small improvement but it’s removing a speedbump in the workflow :>
And I tend to move things around a lot when I draw

I see, thank you for clarifying.

I see what you mean. It is true, that it is confusing.
And if the transform tool can do it, why does the move tool can not?

I do agree, that that it is annoying. But I never use the move tool. I do not know why it is even there, because the transform-tool does it all.

Therefore I would like to suggest, the removal of that move tool, adding “move without transforming” to the transform tool, as tool preference and setting it as default preference. Basically merging both tools into one. And it would be nice, if the tranform tool could remember my last preference I used, when using the transform tool.

What do you think?

Thanks for the reminder of the transform tool. Photoshop doesn’t work in any way.

This is a feature that I really wanted. I actually added to me own local version of Krita, but contributing seems complicated so I’m still going to +1 this change here. It’s also not a particularly technically difficult change. Just have to keep in mind that groups should also be moved together and locked layers should be skipped (but not invisible ones)

Be sure to add your vote at the top. I notice there are only 4 votes in the 2 years this has been a feature request.

This is not a particularly complicated feature and it’s implementation is not hard. I’ve already done it, but are pull request accepted for Krita without having a certain developer status or something? I’m not familiar with the KDE PR process.

Generally speaking, the Krita developers appreciate any well-documented contribution, and if it meets the standards, I believe there’s a good chance it will be accepted.

@Drawpile, I remember you gave advice on this recently, could help please @dmitsuki with this request? Thank you!

Michelist

You don’t need special status, you can just fork the repository and make a merge request https://invent.kde.org/graphics/krita/-/merge_requests. I don’t think that process is particularly complicated or different from any other project out there, but if you have questions about it, you can ask me here or send me a direct message.

Developer status is only needed if you want to be able to push to the production branches of projects, which is not necessary for contributors.