BenJamesBen

Thanks for that clarification. There was another mistake in my first draft fix. Because of floating point math, it would sometimes cause the number of expected bottom buttons to be...

Using `points.realBustPoint` and ```js if (options.bustAlignedButtons) { const fulllen = points.cfNeck.dist(points.cfHips) const toplen = points.cfNeck.dist(points.cfBust) const toppercentage = toplen / fulllen const topnumberbuttons = Math.round(options.buttons * toppercentage) const buttonspacing =...

I am still working on this Enhancement request. I have been doing work on it every few days or so, and the code has been "done" for a while. However,...

Using the measurements from #2595 and uncommenting debug code in Titan, it looks like the problem might be occurring during the iterative crossSeam fit process, both "Remedy A: Slash and...

The proposed fix is to iterate the front and back crossSeam adjustments for as many times as they produce improved results. Once we see that they are starting to produce...

The changes in #2704 address this bug. However, additional "check if points are inside or outside the seamline" code will need to be added to the PR for the seatIn...

Initial analysis indicates that this might be Bug #2516 which was recently fixed via PR #2542 . @joostdecock Has PR #2542 already been deployed to freesewing.org? If no, then we...

FreeSewing v2.22 was recently deployed on freesewing.org, and now this error is no longer seen on freesewing.org. My conclusion is that this was indeed a duplicate of #2516 , it...

- Layout/export problems still occur when you move pieces off the left of column A or above row 1. I assume this is still a known issue, not addressed by...

When I move a part to the left of column A (for example half on, half off), it remains in that halfway-off-the-page position. It does not automatically move or snap...