Bug 357619 - Moving a layer and undoing the move positions the layer in the wrong place.
Summary: Moving a layer and undoing the move positions the layer in the wrong place.
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Tools (other bugs)
Version First Reported In: 2.9.10
Platform: unspecified Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
: 357488 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-01-06 14:34 UTC by kjdavila4
Modified: 2016-04-01 14:44 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description kjdavila4 2016-01-06 14:34:05 UTC 
Crash when I move a layer and I want to undo the action but the layer is positioned somewhere else and it is not positioned how it was before. 
This only happens when I undo for moving a layer but for the rest of the tools is ok.

Reproducible: Always

Steps to Reproduce:
1. Click the Move a Layer Tool
2. Position the layer to the left or right
3. Undo (Ctrl + Z). 

Actual Results:  
The layer is positioned somewhere else instead of being in the last positioned.

Expected Results:  
It should undo how the layer was positioned before.
Comment 1 wolthera 2016-01-06 17:46:05 UTC 
Hey there,

I think this bug was fixed in the current code, so could you check the 3.0 alpha when it comes out if the bug is resolved? If not, open this bug report again :)
Comment 2 Halla Rempt 2016-01-10 11:07:13 UTC 
Hm, I can definitely reproduce this on Windows for 2.9, but, interestingly enough, not with Linux. I can verify that the bug is fixed in 3.0, but I'm not sure whether it's a fix we can backport to 2.9.
Comment 3 Halla Rempt 2016-01-10 11:16:35 UTC 
*** Bug 357488 has been marked as a duplicate of this bug. ***
Comment 4 kjdavila4 2016-01-10 18:15:12 UTC 
Thank you for the comments wolthera and Boudewijin. So when will the version 3.0 be available?
Comment 5 zottg 2016-01-18 00:26:37 UTC 
This is fixed for me in the 3.0 pre alpha. Can reporter confirm as well?
Thanks!