A few days back I wrote about how I was getting the “critical error” window when I tried to open one of my .sm2d files. Well, turns out I’m having the same problem with almost all of the patterns I make, and it’s getting kinda frustrating because I cannot finish any project. At this point when I start a new pattern, I feel like I’m walking a tight rope, second guessing myself and crossing my fingers so that the program won’t crash. As I said before, is there anything I’m doing wrong? Could it be that my patterns have too many pieces or something like that? I really love Seamly and just as I was getting the hang of it, I’m facing this issue.
Few! That was long. Any replies or suggestions will be very much appreciated. Thanks a lot in advance 
Hello, @Gonzalo_Jimenez
I’m sorry that you’re having this problem. Can you send me a .sm2d file with it’s measurement file, please? So that I can have a look? If you don’t want to post them on the forum, you can private message me by clicking on my profile photo & selecting the Message button.
Not likely.
As @Grace pointed out you can post your pattern and we can have a look.
Not likely.
As @Grace pointed out you can post your pattern and we can have a look.
@Gonzalo_Jimenez Is it this error: “file error exception:Content of attribute lineWeight does not match its type definition: String content is not listed in the enumeration facet”
Have you updated to the latest version?
Hello! Sure, if I’m able to, I’ll PM you the pattern and measurements file. Thanks! 
Hi! Yes, that’s the message I get most of the times. As for the update, I downloaded the latest version a few weeks back, I don’t know it there is a new one already? I’m checking that out. Thanks!
There’s a new update every Monday.
There’s a new build every Monday… that doesn’t always mean there’s any new updates in it. This week there was. 
I’ve just installed the latest update and… same thing. I’ve just gotten the same error on a file I created last Thursday. I’m sending you one of my (many) corrupted files via, I hope there’s a solution. Thanks! Edit: Actually I cannot send attached files yet…
I checked your user level… you should be able to send attachments now.
Also if you post a screenscap of any error messages that would be helpful to.
Sure! This are the two errors I’ve been getting.
This one says something about line 161 column 131, I’m assuming it refers to the “programming” of the file? And this is the second one. Even if the files couldn’t be repaired, I’d love to know if there’s any way to avoid that happening. Now, when I make a new pattern, I try not to delete any point/line/curve on the pattern and rather hiding it inside a group, I don’t know if that could help? Anyway, thank you so much for your time!
I sent you your fixed file back via PM. The pattern files are pretty forgiving and we can usualy fix them without losing much is anything at all. In this case it was my bad as when I updated the internal paths recently I used the incorrect strings of “Black” instead of"black" and “1.00” instead of “1” for the default data value. That’s why was throwing the execption for the lineColor on line 161. The color part was fixed with last monday’s release, but I didn’t realize the lineWeight has an issue too. Until I fix the line weight I suggest use a different color & line weight other than Black and 1.00 so the internal path don’t use the bad default values.
I’m sure that either @Douglas or I can fix your files for you if you send both pattern files & measurement files.
Other than that… If you do delete something that has dependants, you normally get the message to either Undo, Fix the Formula or to Cancel. A small tip from a long time user… NEVER click the Cancel. And, if you do, go to File and re-open the pattern. When you get a message that the pattern is open in another screen, click on Ignore. This will open the Autosaved pattern before you deleted anything.
With the file open, go back to the previous one and close it. When asked if you’d like to save it, cancel the saving so that the blanked out pattern just closes.
Another small tip… before you do anything that you’re not certain about, always click on the Save icon or hold down the Crtl/Cmd key & press S - so that you know that you have a backup just before you do something iffy, just in case.
Already fixed.
But just as a note… if you need to ever fix other files… colors should always be lower case with older versions before last week… and decimal numbers should not have any trailing zeros. So “1.00” should be “1”, “1.20” should be “1.2”… “0.90” should be “0.9”, etc.
Already fixed.
But just as a note… if you need to ever fix other files… colors should always be lower case with older versions before last week… and decimal numbers should not have any trailing zeros. So “1.00” should be “1”, “1.20” should be “1.2”… “0.90” should be “0.9”, etc.
Thank you so so much!
Well, now that I know it it makes perfect sense, because I usually had problems with my files only after I added internal paths. Knowing that is actually very helpful, because I opened a copy of the file through notepad and with “find and replace” I replaced the “Black” by “black” and the “1.00” by “1” and now the file is working again Thanks for your time, you helped a lot!!
Thank you both so much!
Yes, I’ve seen that message once or twice. I’ll take good note of your advice