Bug 398930

Summary: transform tool does not work on multiple layers
Product: [Applications] krita Reporter: wkg28406
Component: Tools/TransformAssignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: halla, tamtamy.tymona
Priority: NOR    
Version First Reported In: nightly build (please specify the git hash!)   
Target Milestone: ---   
Platform: Appimage   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: video showing transform and move tool

Description wkg28406 2018-09-21 20:00:09 UTC
Created attachment 115156 [details]
video showing transform and move tool

krita-4.2.0-pre-alpha-127857b-x86_64.appimage

Tested with fresh configuration (removing existing ~/.local/share/krita, ~/.config/krita*)

Reproducible: Always

Steps:
1. Create new document (ctrl+n)
2. Draw object on layer 2
3. Create new layer (insert)
4. Draw object on layer 3
5. Select both layers 2 and 3 (using ctrl+left click)
6. Try to transform (ctrl+t) only one of the layers, the last one selected, will work
 
Results:
Transform tool works on multiple layers only if they are grouped, and the group layer is selected.

Expected:
Transform tool to operate on multiple selected layers, regardless of grouping, like the move tool does.

The transform tool explicitly says it operates on a layer or selection, however compared to the move tool it behaves inconsistently, leading to a bad user experience. It is annoying to have to create groups for everything separately if wanting to move or rotate multiple layers quickly.

There is also a long delay when trying to transform on a group of layers.

Video attached.
Comment 1 Halla Rempt 2018-09-27 14:24:12 UTC
It's not that easy. The move tool actually moves stuff. The transform tool transforms only a preview, and you cannot make a preview of a random selection of layers.

Besides, this has been reported before.

*** This bug has been marked as a duplicate of bug 398285 ***
Comment 2 Tiar 2020-06-23 13:59:46 UTC

*** This bug has been marked as a duplicate of bug 371550 ***