just upgraded and now i can’t export pieces to pdf anymore.
is there a fix for this? i’m on a time crunch.
ani 092225.smis (1.2 KB)
homecoming dress.sm2d (69.4 KB)
2 Likes
figured out what happened. the upgrade changed the export file location.
2 Likes
I am now having severe lagging and missing information when i hover on pieces. is this related to the upgrade?
2 Likes
2 Likes
I just checked against the last 2 releases… and my current build - the pattern loads fine?
2 Likes
for some reason this latest version keeps opening 2 seamlys. think it might have something to do with that. it also keeps asking if i want to refresh measurements when that hasn’t changed.
then when i close i get a forced close error.
ani 092225.smis (1.2 KB)
hc dress.sm2d (56.7 KB)
2 Likes
I’m not getting the 2 Seamly’s opening and the refresh measurements, I get a lot of, but not with your pattern, since I didn’t change anything except the measurements file location. Nor do I get the forced close error.
hc dress.sm2d (57.4 KB)
I know “why” the sync measurements randomly pops up… I just don’t “what” is specifically causing a change to the measurement file that’s triggering file changed signal.
// Handle changes made to a measurment file. connect(watcher, &QFileSystemWatcher::fileChanged, this, &MainWindow::MeasurementsChanged);
When a measurement file is loaded it’s added to the watcher list, and when a change is made to the file a fileChanged signal is emitted which is handled by the above connect statement.
To fix it - it’s one of those issues I need to know exactly what will reproduce the issue WITHOUT having actually changed any measurments and saving the file.
2 Likes
It seems that editing (or even opening) the Variables Table triggers it. It could be because I normally click on Refresh after changing a value in the variables, to see that things are still OK after the change.
But the variables are not stored in the measurement file… which is the file that’s being “watched” for changes. I’ve had the sync message pop up just loading a pattern file… I think it’s happened when I already have a pattern file open and I just click ignore? I’ve just have’t figure out exactly what sequence will always trigger the random syncs - other than actually changing & saving the current measurements.
2 Likes
I have same problem, as soon as I open SeamlyMe and the used measurements file from Seamly2D and go back to it I will get the window about the need to sync. I haven’t even changed anything in SeamlyMe, just open and close it.
What always triggers a new prompt for syncing:
- drawing a new element
- alt-tab between different programs (coming back to Seamly2D
- closing and saving Seamly2D
What doesn’t trigger them
- opening or closing Variables window
- deleting or undoing
While this loop of syncing is present the “Sync” inside “Meauserments” menu is available even directly after I sync (it’s greyed out when I open a file in Seamly2D)
What helps
- clicking “no” in the prompt for syncing
After that I can still sync through menu.
If you need more info or testing I will be glad to help.
2 Likes
I just opened the sleeve pattern and changed the size and moved a few point labels around and nothing happened.
I went into the Variables Table and changed a value there from 0.0001 to 0.0002, did the refresh & closed the Variables and look what happened:
Repeated the exercise and it happened again.
3 Likes
What I’ve noticed is that when I open a file Seamly always opens a second window. When I close out of the file I’m working on it’s fine but then when I close the empty file it crashes. I get this error message. Often related to opening history window. I used to be able to open the history window pick where I want to insert a line then close history window. Now when I click on something after I open history window the window moves behind and I need to minimize the main window and move the history window into view to click ok and move on. Maybe it’s two separate issues? but it’s also lagging, for example when I click on properties to edit something once I enter points in I have to wait probably 10 seconds for OK to light up.
error message.pdf (145.0 KB)
1 Like
Just for information.
I work often with two windows. Just by switching e.g. clicking on the non-active window the snyc pop up shows up.
3 Likes