Hi , @Grace@Douglas , and all the amazing creative minds here,
God bless you all for the helpful suggestions so far — I must say they’ve really been a huge help to me. However, I’ve hit a bit of a roadblock and haven’t found a solution yet.
I’ve been working on a pattern file for a while now, and I’ve noticed that it takes a long time to load when moving from one node to another. (I’m not the best at explaining things, so I hope someone understands what I mean.) This lag is slowing down the drafting process significantly, and it’s becoming quite frustrating. I suspect the issue might be due to having too many patterns in one file — though I’m open to correction.
So, I was wondering: is there a way to select at least one pattern block and move it into a new file to continue working on it, without having to start from scratch?
There are many factors that can affect the speed of the CPU while working on a pattern. The CPU and clock speed, the amount of RAM, how many draft tools are in the pattern file, the version of the Seamly2D app.
Older versions of the app had a problem with repainting the control paints recusively which would eat up much ofthe CPU usage. That shoudl be fixed in recentversions, but you could try toggling the view of the control points off ans see if that makes a difference:
One issue I still have not been ableto figure out, is the CPU usage jumps a bit when you are zoomed in past 100%. Again it’s probably a recursive painting of the points and name issue I haven’t been ableto track down - yet.
Besides what @Douglas has mentioned, somewhere in the past year or so, there was a similar issue where the pattern found itself in a continuous refresh cycle because of (I can’t quite remember) 2 nodes being incorrectly selected or a curve handle that was pointing the wrong way around… Something like that.
If you delete all of your pattern pieces… and create one. How does it behave? Make a copy of your working file first
Other than that, you’re welcome to send your file and measurements to @Douglas or myself, in private a message, so that we can have a look.
