I am not sure, bt I doubt this is intended. Shift is intended for constraining direction, isnt it?. But no matter on which layer I am, if I have the move tool selected and press Shift and then try to move, all layers are moved. It works as expected if I first move and then initiate Shift. Again, not if I press SHIFT first and then move.
What application is this in?
Oh sorry I thought this is all about Krita
1 Like
This forum is for all KDE projects, so it’s good to specify what project your question is about so the right people find it. I added the Krita tag, you could also put Krita somewhere in the title if you want.
In the Krita 5.3.1 AppImage on Arch Linux, this also happens for me exactly as described. However, in Krita 5.3.3 on Android, it works as expected - holding SHIFT before moving constrains the movement.
Which version of Krita are you using and on which platform?
You may just need to update to the latest stable version, 5.3.3.
If you’re using 6.xx, that version is very usable, but not considered as stable.
PS: The 5.3.2.xx to 5.3.3 AppImages on Arch Linux fail to launch for me, which is why I use 5.3.1. But it may launch just fine for you, so test it out if not already using it.
Using the latest from the website . If I recall it is 5.3.3 .
This is a severe bug then. In the previous build I couldn’t even undo it and I had a lot of layers of very high resolution where assets for a platformer were aligned to a grid. I wasn’t aware that the undo didn’t work so everything was off and I couldn’t understand why first . The latest version at least has the undo working .
You can submit a bug report for it at https://bugs.kde.org