Summary: | Krita doesn't save clone layers correctly | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Torio Mlshi <mlshi> |
Component: | File formats | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | halla |
Priority: | NOR | ||
Version: | git master (please specify the git hash!) | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | This is a bugfixing patch |
Description
Torio Mlshi
2011-10-08 15:58:08 UTC
I can confirm, and this is a critical bug, since it leads to dataloss. Torio -- didn't you already have a patch for this bug? Created attachment 64584 [details]
This is a bugfixing patch
2boud:
Yes, I've just finished it today ;) It is implemented not with filenames (as they are not constant and generated each time on saving), but with new field - uuid.
Bug seems to be fixed in this commit, but I think that krita/dtd/krita.dtd should also be fixed to represent changes. So I wonder if uuid should be marked as required or impiled (for compatibility reasons)?
Interesting patch... Can you put it on git.reviewboard.kde.org to make it easy for everyone else to look at it as well. I think I agree with using uuid's here instead of layernames. I'm not sure it needs a change to the dtd, but we carefully need to make sure old versions of krita can load files created this way and vice versa. |