Hello! I am new on Seamly2D, have started using the software few days ago. Thank you very much for creating it! At first I was using Valentina, then I found there was Sealy2D now. I have problems when drawing curve paths in Seamly, because the program seam to freeze for a few seconds and I can not adjust the curve in the real time, I can just move the handles and then wait for the result. It’s annoying and it takes ages to draw a desired shape. What can be the reason? I don’t experience any problems drawing straight lines and other paths, everything works quickly. Just the curve tool…It was working smoothly in the Valentina, but for some strange reason it doesn’t work in this Seamly2D version. Did anyone have the same problem and what was the solution?
Hi @huraganka, I haven’t come across this problem. Perhaps because I always just put the curve in ‘any-how’ and then open the options of the curve and put in more formula based lengths and angles.
If you could past a picture of the version of Seamly2D that you’re using and what platform you are working on (I’m on Windows 10), perhaps someone will be able to help you.
Hi @Grace, thanks for answering! That’s the version of Seamly2D I’m using: 
and I’m on MacBook with OS X Yosemite. I’m drawing curves manually mostly because I want to try different shape options, the way I am drawing for instance on Adobe Illustrator. I am still not very familiar with Seamly2D and I am constantly trying new things and options, maybe I will need to learn to work more on formulas than direct drawing.
Thank you. I’m on an older version and Windows, so I’m hoping one of the programmers will see this and perhaps be able to see if this is a program issue or what.
In the meantime, here’s a little toy that I’ve tried to make that also uses the handles to change the curves. Perhaps you can check on it whether they move smoothly for you: Bird Soft Toy pattern.val (17.5 KB)
Hey 
I’ve had the software 2 days, and overall love it. I have been experiencing the same issue with curves however, so thought I’d chime in so dev’s know it’s more than one of us.
I am also running a 2014 MacBook Pro with High Sierra 10.13.6 My version of Seamly2D is 0.6.0.1, build revision 12b271be4cdf.
I have the same problem with curves stalling or even crashing the software. Sometimes it’s ok, sometimes as soon as you select a curve everything stops for a few minutes, until ultimately the software crashes and closes. When it does work, grabbing the curve or a handle gets the macs fans on really quickly. I found that if I could make an adjustment to the curve with the formula box first, then move to grabbing the curve or handle, it seemed to be a lot happier and run smoother.
I’ve been good about saving, so hasn’t cost too much of any pattern.
Cheers,
Lee
Hi and welcome, @LeRich. It seems this is a Mac problem. I have Windows so I can’t test this.
Can you please post some screenshots of the error and what you are doing when the error occurs? Also, the .val and .vit files will be helpful for the person testing and checking the problem to recreate it.
Thank you
Hi @Grace,
Thank you for your reply 
20:10pm Here is a screenshot just after I selected the curve A4-A16-A12-A11.
20:10pm The curve went red, showing it had been selected.
<a class=“attachment” href=">
20:11 From then, there was no response from Seamly2D for around 20 seconds. At this point the cursor changed to the ‘StarTrek’ arrow symbol, with a small red line at an angle below it - I believe this is the point control tool. I tried to select a handle, but there was no response from the program, so I released the mouse click.
20:18 From this point there were 7 minutes where nothing happened, until the next screen shot when the curve jumped and changed in shape. From the moment I selected the curve, the cooling fans came on, and remained on for the durations above until the curve moved. The fans then slowed back to normal again.
20:20 An addendum - when moving screens around to get the screen shot, this message just popped up from Seamly2D:
‘QGestureManager::deliverEvent: could not find the target for gesture’
I hope this helps - sorry for the multiple edits, I’m still figuring how to use the drag and drop placement of files and pictures!
If anything else is needed, please just say - I’ll send whatever I can to help
SC_BodiceSlope_Pattern.val (8.3 KB)
TestMeasurements.vit (1.1 KB)
Thank you for all the info and screenshots. I’ve manages to drag the handles around with no problem, delays or anything. But then, I’m on Windows 10.
I’ve also remade the curve (in blue) with no problems:
I’m going to create an issue so that one of the programming people can have a look and see if they can find a solution.
Issue created.
Hi @LeRich,
Typically, MacBooks are considered a bit underpowered for graphics software, but we’d like to improve our software performance to minimize these issues.
Thanks for doing such a beautiful job illustrating the problem.
Hello everyone!
I am very sorry to answer to this thread with two years of delay but I have the same issue and the same computer. I have the most recent Seamly2D update but the problem is still there.
Anyway I found out that if I use an external mouse instead of the trackpad I can work with curve handles perfectly.
I hope it may helps you all!
Susan… we could probably improve performance with “handling” the curves by using a pref for the accuracy of the curve as it drawn on the screen. I’m sure you are aware that the curves are actually made up of sections of straight lines… the smaller and more lines the greater the accuracy, but the more CPU required. I believe it currently is a fixed value.
Comparatively speaking this should be relatively simple to implement.
@Douglas - Could you add an issue to github? Curves are actually polylines, and it makes sense to have responsive “subline” lengths.
No problem. Although I think we have two separate issues… one related to issue “Creating curves on Mac OS Sierra #160” where GraceDM reported
“This error seems to have appeared and disappeared while moving around the screen: ‘QGestureManager::deliverEvent: could not find the target for gesture’”
which appears to tie into what Yolo reported…
And then there’s the general performance issue some may experience with slower computers . I’ll create a new issue regarding the curve geometry issue. The (MacOs?) trackpad / gesture issue may have to wait - I’m at a disadvantage not having access to a Mac, and not sure if I can replicate that issue on either of my Windows laptops.
Yeah It’s a problem not having a Mac so we can’t reproduce the problem, and can’t test any fixes. I’d like to get one, but they are just too pricey.