Version: svn trunk (using KDE 4.7.1) OS: Linux Clone layers are saved referencing their targets by names, so when there are two (or more) layers with the same name, clone layers are not saved correctly. I can see two ways of solving this: 1. Warn user when (or even doing so) layers with same name appear. 2. Change saving clone layers. For example save not name of target, but its filename (which appear to be unique). Reproducible: Always Steps to Reproduce: 1. Create two layers with the same name. 2. Create clone layers to each of them. 3. Save file. 4. Open it again. Actual Results: Both clone layers are pointing to one layer. Expected Results: Clone layers should work as before saving/opening: point to different layers.
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.