BenJamesBen

No, if that is the intended behavior, it is fine. That being the case, I will ignore any layout/export errors that occur after moving pieces out of bounds. (I managed...

I am able to reproduce the issue, but not 100% reliably. I believe the steps to reproduce are: 1. With Bob, move the bib part off of the screen up...

I am able to reproduce the problem on freesewing.org. In lab.freesewing.dev, I note that there are 3 Advanced options with values as "No constant val yet" which is likely related...

I note that the following change fixes the issue in the localhost version of the lab: ```diff --- a/designs/teagan/config/index.js +++ b/designs/teagan/config/index.js @@ -37,9 +37,9 @@ const config = { bicepsEase:...

The correct Lab link is: https://lab.freesewing.dev/v/next/unice?from=github&preload=44ce421b43486e6c26cf5e17b60ba02f ``` Error: 0 | Called Path.shiftAlong(distance) with a distance of NaN but Path.length() is only 94.82767910170298 1 | Unable to draft part back2 Warning:...

The way the code is written in `elastic.js`, there will always be only 1 notch on the back leg opening. There is code that was intended to provide 2 notches,...

This bug occurs in the v2 version of Unice. It has been fixed in the v3 version.

Many of the same variable names for points are re-used in different parts for different purposes, making it seem as if there is more duplication than there actually is. There...

In case anyone was curious, the generated patterns look like this: 

The problem is also seen on v2.freesewing.dev. For example: https://v2.freesewing.dev/blog/rollup-to-esbuild