Bug 419891 - Undo&redo causing problems on canvas
Summary: Undo&redo causing problems on canvas
Status: RESOLVED DUPLICATE of bug 419372
Alias: None
Product: krita
Classification: Applications
Component: General (show other bugs)
Version: nightly build (please specify the git hash!)
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Dmitry Kazakov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-09 21:36 UTC by acc4commissions
Modified: 2020-06-02 12:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description acc4commissions 2020-04-09 21:36:01 UTC
SUMMARY
git b649a22

https://imgur.com/YYeHVkb
I'm not sure how to describe this. Hope the video in the link helps.

In the video, I basically : 

1. Painted few strokes over the each other.
2. Repeated undoing the process&redoing the process with shortcut keys. 

OBSERVED RESULT
1- Some projections appear.
2- Sometimes pressing undo or redo doesn't do the job. It behaves as if the document was saved and opened again at a certain point in the process and the undo+redo data from the point is gone.

EXPECTED RESULT


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

ADDITIONAL INFORMATION

It doesn't happen in 4.2.9.
Comment 1 acc4commissions 2020-04-09 21:38:07 UTC
Some 'projections' stays on the canvas when I make the layer invisible.
Comment 2 Lynx3d 2020-04-10 14:35:31 UTC
Yes I can confirm on my Linux build too, undo is severely broken on master. To me it seems to happen mostly on the last step you can undo, it fails to restore.

Bug 419372 speaks of a visual bug, but this is definitely not a repaint issue, the canvas content is messed up for me.
Comment 3 Dmitry Kazakov 2020-06-02 12:15:27 UTC
Hi, acc4commissions!

I think the bug has been fixed in 63af6bb0961dcd07b89e8150c6e2644dafb0e46c, with fixed bug 419372. If you still experience the bug in Krita 4.3 Beta1 or Beta2, please reopen the bug :)

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