We no longer have to manually fix user’s broken patterns with reagrds to the out of order <groups> and <images> blocks.
The next release will automatically repair a broken file. Just have the user update Seamly.
We no longer have to manually fix user’s broken patterns with reagrds to the out of order <groups> and <images> blocks.
The next release will automatically repair a broken file. Just have the user update Seamly.
This is great! since there seems to be something that still occasionally causes files to have this corruption.
![]()
Yes. I figured I’d let you and Grace know since the 3 of us are the ones generally fixing users files. @seam did the initial fix to swap the groups and images blocks if they were in the wrong order. I added a fix to create empty blocks for any missing groups and / or images block so the files are always valid.
You are correct. Need to check version and only apply if >= <mages> was added to schema.
Easy fix… just have to check if the loaded version is older than the image import schema.
const int current_ver = GetVersion(getVersionStr()); const int image_import_ver = GetVersion(QStringLiteral("0.7.1")); // Image import introduced. if (current_ver >= image_import_ver) { if (fixGroupsOrder()) { saveRepairedCopy(); } }