Parse Error: Unexpected token

Hello, new Seamly user here with what may be a user error on my part. I’ve checked other posts and haven’t found one that exactly seems to be the same situation:

Say, I make a new variable. I can tab over the “Line lengths” and copy the name of a line I want, for instance “Line_A_A1”. When I drop this into the Formula blank it pulls in the value as expected. However if I close the screen and reopen it, it says: “Error(cm) Parser error: Unexpected token “Line_A_A1” found at position 0”

It is like it is getting the value but not “keeping it” if that makes any sense. My purpose is to keep some of my more complicated formulas out of the pattern and in an easy to find/reference location. For instance I might sum the lengths of the curves around a neckline or arm scye for personal reference while working or for use in other places in my file. I can think of some work arounds but they seem like nasty hacks.

Also, I am using the current build for Windows.

Thanks!

The copy feature comes with a cavaet… you have to know if the tool variable you are copying is a valid variable to paste in another tool’s formula. That’s why we recomend new users to use the fx Editor as it will filter out imvalid tools.

The application is built on the principle of a linear timeline… that is tools can only access tools that were created before it. You can’t reference tools that have not been created yet as far as any given tool is concerned.

Thanks for the clarification. My backup plan is to put some lines in a (usually hidden) group on the pattern and make the length of these the result of a calculation I’ll need. For instance, summing all the curves in a neck line. Later I can reference any of these as a kind of simulated variable. Not elegant, but might be the best I can do. I’ll do some digging through the forum to see how others handle situations like these.

Thanks again!

For now that’s pretty much how we’ve handled comparing 2 lemgths… such as a sleeve to an armhole.

Again based on the linear aspect of the app… create your comparisiom lines last as they will then have access to the rest of the tool variables It’s also common that we draft everything in 1 block and use the groups to hide parts you don’t need to see. For ex: Draft the front & back of a jacket then the sleeve… that way the sleeve has access to the front and back variables. While working on the sleev you can hide the front and back parts - assuming you create a front and back group.