Error on "groups" element

Muller&Sohn-Trousers.sm2d (17.6 KB)

I have an issue with opening this file which I made a few days ago.

When I try to open it now I get this error:

The only thing I did was open a file in a text editor to try and see what are some object dependencies and I don’t think I changed any of the text in it.

2 Likes

You could have an older version that had a bug with the order of writing the groups and images tags. Because the schema validation failed, the app is throwing a file exception.

Needs to be this:

Newer builds implicitly write empty groups and images tags when creating a new block.

BTW… For future reference. We can’t test patterns without the measurements.

3 Likes

It’s a pretty new version though. I will download a newer one.

2 Likes

Did you start the pattern under a previous version… and then add groups with your current version?

Like I said newer versions will implicitly write empty tags in the correct order:

2 Likes

No it was made with the same executable. It’s also not the first time I get this error. I had it happen before and it ended up forcing me to discard the pattern since I did not know. I have downloaded the release from 2 days ago so hopefully that won’t happen again now

2 Likes

@Olaru_Iustin Did you get your pattern to work?

2 Likes

Yes, if I go into the fifle and switch the groups tag to be above the images tags then the file opens again.

3 Likes

So then the question is - assuming you created the pattern with a recent version and have not edited the file - how did the one (empty) groups tag get out of order?

Did you by chance delete any groups? Not that it would normally remove a groups tag and move it after the images tag. I just need to figure out if this is still an issue or it’s confined to the 1 or 2 releases a few months back.

2 Likes

Right so I did try around the group functionality. I tried making a group and then adding a point to it and then deleting the group. Nothing more than this, but perhaps this is where the issue happened. I think that might have been what caused it also last time when it happened.

2 Likes