Bug 212235

Summary: default pixels becomes transparent after an undo
Product: [Applications] krita Reporter: enkithan
Component: GeneralAssignee: Dmitry Kazakov <dimula73>
Status: RESOLVED FIXED    
Severity: normal CC: dimula73, halla, user581
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description enkithan 2009-10-28 21:46:46 UTC
Version:           2.2 Alpha 1 (using 4.3.2 (KDE 4.3.2), Arch Linux)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.31-ARCH

1.create a new 1000*1000 pixel custom white sRGB built-in image
2.paint something
3.undo -> white pixel becomes transparent
4.redo -> only paint pixel are opaque, white pixels are still transparent.
note: the bug does not happens with default rgb template.
Comment 1 Dmitry Kazakov 2009-10-28 21:58:13 UTC
A transaction is not created during creation of a new custom image. tiles3 is quite sensitive for that =). Where is this "Custom image creation code" placed?

PS: Templates are loaded from files through a datamanager, that is why they work well as a transaction is created interally.
Comment 2 Halla Rempt 2009-10-29 07:41:07 UTC
That's in KisDoc2::newImage.
Comment 3 Halla Rempt 2009-10-31 10:21:17 UTC
*** Bug 212460 has been marked as a duplicate of this bug. ***
Comment 4 Dmitry Kazakov 2009-10-31 23:32:52 UTC
SVN commit 1043167 by dkazakov:

Transactions was not being created during creation of the image.
Fixed a bug in KisTiledDataManager::clear() as well.

BUG:212235



 M  +16 -6     image/tiles3/kis_tiled_data_manager.cc  
 M  +9 -28     ui/kis_doc2.cc  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1043167