Critical error : Exception draw is not defined in the scope


#1

Hi,

I have this error message : Critical error : Exception draw is not defined in the scope 2019-05-14_15-20-50

How can I fix the file? See the file here : 6 - Leggings - patron base_v1.val (49.6 KB)

I tried to open the file with Notepad++ to check if I could identify the problem, but I can’t…

Thanks for your help!

Simon


#2

Hi Simon, I ran your pattern through the parser at seamly.cloud and produced this listing seamly-tmp.pdf (109.1 KB) of the steps you used in construction. Perhaps this will help you to identify the problem. Please take a look and let me know whether it helps.

Kim


#3

Hi Kim,

Thank you, but I don’t know if it helps.

At some point, I remember erasing some points and having an error code but the pattern was still working…

Is there a way to identify and change the “value in line 3 column 31” ? It seems to be the problem in the error message.


#4

If you are able to make a earlier version of the file, let’s say at the page 16, it would be great. I think the problem was in the last steps of the pattern…

Thanks!


#5

@simoncotelapointe,

I need to know how you produced the file. I opened it with an xml editor and compared it against other properly formed files created by seamly2D and it appears that the file was damaged during an attempt to manually edit it with Notepad. We really can’t support all possible errors that could be introduced by such manual editing.

If I am mistaken and the file was formed in this way by the seamly2d program, it would be really helpful if you could help to reproduce the steps you used to create it.

That said, I fixed what appeared to me to be the issue with the file but I have no way to test it without the .vit file that you use with it. Here is the version I corrected.

The issue was that the xml statements that belong in the front of the file before the <draw…> statement were moved to the outside of that clause, after the < / draw >. Here is the corrected file. 6 - Leggings - patron base_v1-AA.val (49.6 KB) If you want me to do anything else with it, I will need to have the .vit file that goes with it.


#6

Thanks a lot! It is working.

I’ve opened the file in Notepad but I didn’t make any modification with Notepad as far as I know, because the error occured before I opened it with Notepad.

It’s hard to reproduce the steps I used to create the pattern. It is a derivative from another one : 5 - Short shorts Block - patron base_skintight_v2.val (30.6 KB)


#7

Interesting. I have never seen this type of error before. @Grace have you seen an error like this? It seems like an easy thing to do by mistake in a text editor but I have never seen it in a file generated by Seamly2D. (compare Leggings - patron base_v1.val, with the version that I fixed and returned with the name Leggings -patron base_v1-AA.val)

@simoncotelapointe, please let us know if you see a similar problem in the future and provide if you can the “before” file that works along with a description of what you were doing before it failed. If you can help us to reproduce the error without using a plain text editor such as notepad, I will add it to the issue list.

As I said, we are unable to support issues caused by modifying the xml source of a pattern file manually. That said, I suggest that if you must open the xml source with an editor it is probably safer to use something such as XML Copy Editor 1.2.1.3 (open source available at http://xml-copy-editor.sourceforge.net). Use of such a tool will show you a more readable view of the xml.


#8

Hi @kmf, yes, I have seen it before where the opening arguments are at the end of the document. Can’t remember if it was last year or the year before. What caused it the last time was that the person tried to copy and paste parts of one pattern into another pattern instead of opening the pattern to be copied, renaming it and building on it (I don’t know if this makes sense to you). But I repaired it and didn’t add it to bugs because I didn’t feel that it was one :slight_smile:


#9

It probably should be written up as an issue and fixed. before that, it is best if we can find a way to reproduce it.


#10

As I said, the previous one was because someone was copying & pasting bits and pieces into the file using a line editor, which isn’t the case here. And also, the previous one was on a previous version of Seamly2D, if I recall.

@simoncotelapointe, please, what version of Seamly2D are you working with?