Bug 404047

Summary: "Move tool" slowness comparing to "Transform tool"
Product: [Applications] krita Reporter: Darii <darikzen>
Component: Tools/MoveAssignee: Krita Bugs <krita-bugs-null>
Status: CLOSED NOT A BUG    
Severity: normal CC: freebox64, halla
Priority: NOR    
Version First Reported In: 4.1.7   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: example
Video

Description Darii 2019-02-07 05:10:55 UTC
Created attachment 117906 [details]
example

I can't get why moving something using "move tool" works much worse than same action while with "transform a layer or selection" tool.

STEPS TO REPRODUCE
1. Choose some object.
2. Use "transform a layer or selection tool"
3. ctrl+z
4. Use "move tool" to make the same

OBSERVED RESULT
 worse functionality

EXPECTED RESULT
 same functionality


SOFTWARE/OS VERSIONS
Windows: 
MacOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 mvowada 2019-02-07 07:27:58 UTC
Created attachment 117908 [details]
Video

(Tested with 4.2.0-pre-alpha (git 86c58a3) - Ubuntu 14.04 - RAM 8GB - GeForce 9800 GT/PCIe/SSE2)

I think it's because the "Move Tool (T)" moves the whole layer not just a part of it as the Transform Tool does. (See video)

    1. fresh configs
    2. start Krita
    3. create a new document: 1920 x 1080 px / 72 ppi / 8-bit
    4. paint some strokes
    5. use the Move Tool (T) to move the layer

Actual Results: refreshing of the canvas doesn't catch up when moving the layer with the "Move Tool".
Expected: no lags when moving a layer?


Note: with more complex layer set-ups it gets worse.
Comment 2 mvowada 2019-02-07 07:32:48 UTC
I'm going to confirm this bug. Please, feel free to change the status of this report if you think it is an expected behaviour. Thanks
Comment 3 Halla Rempt 2019-02-07 10:08:00 UTC
It's slower because it doesn't put a preview overlay on top of the image. That makes it more accurate, but the entire image has to be recalculated for every pixel you move a layer. This is not a bug, it's just the way things are.