Hello! I would really appreciate if someone could help me: I was working on a pattern, and when I tried to undo an “unite pieces” operation, the software presented this message"Error parsing file ExceptionObjectError: Error creating or updating a piece path" After that, I could not open the file anymore. How this happened? How can I prevent from happening again? I lost 2 ours of work, and I really would like to know how could I avoid the same error in future? Can someone help me, please? Thanks in advance.
2 Likes
Hi @C.A_PELLA Welcome to the Forum!
It is possible to fix the file so that it will work again using a txt editor. One of us would be happy to do that for you if you upload it here. Preferably along with the measurements file so that we can make sure we did it right before sending it back.
In the future, my advice is to preferably not use the Union Tool, failing that not to have Seamly delete the original pieces, failing that not to delete anything which you have used the Union Tool on.
Also be sure to use the latest Seamly release. Someday that issue will be fixed, but the code’s a bit convoluted.
2 Likes
[quote=“Pneumarian, post:2, topic:12733”] Also be sure to use the latest Seamly release. Someday that issue will be fixed, [/quote]
You can post your pattern(s) and an measurements and one of us can fix the pattern. If you don’t want to post the pattenr publically you can PM me the pattern and I’ll fix it.
With that being said… if you used the Union tool with any pieces that have Internal Paths end then tried to Undo there is going to be a dereferencing issue with the IPath. I have been working on the Internal Path tool, and have that issue fixed. Hopefully the fix will be in the next release.
That is a bit of an understatement. The Internal Path (along with the Anchor Point) tool has been the hardest to unravel, dealing with the nested Undo commands between the nodes, ipaths, and pieces; and keeping those in sync with the DOM doc, container, and graphic item display.
3 Likes
Thank you very much! I did the same pattern again, so I appreciate your offer for fixing it, but there’s no need of it anymore. If I understood correctly, there’s a bug in the operation “unite pieces” followed by an “undo” command, so, will be better not use this in future. I’m using the soft Linux version Endless OS, and since I’m talking to you, I have a suggestion: in Endless OS, when I open an edit window like the usual windows for manipulate the math, or any other auxiliary window, except the calculator, these windows can’t be moved by any means. They open in the middle of the screen, and frequently I have to close them only to look a hidden underneath point name. I think this doesn’t happen in the Windows operational system, if it is something you guys can fix for the Endless OS version, will be great. Thanks again for the help! I love this software!
2 Likes
I haven’t used Endless, but I have used at least one distro in which I had to make sure that locking sub windows to their parent window was turned off. I don’t remember if that was Ubuntu, Devuan, or Chrome Debian VM. I might be3 able to check tomorrow.
1 Like
I lnow the Union tools has some quirks in it, but can’ t say for sure if it has any particular bugs. The Undo and delete bugs I know about, and I have likely fixed them in the Internal Path tool, not the Union tool.
That being said, I will be updating the Union at some point, and in the mean time you can more or less accomplish what the Union tool does in draft mode. It’s just a little more work.
Not sure if there’s a difference on any Linux systems, but there is a Seamly2D setting for what position you want the dialogs to open at, as well as on option to open on a second screen… the default is center, no second screen.
I would think this is an issue on the Linux OS side, as there’s nothing in the Qt code that prevents (modal) dialogs in the app from moving. I would check and see if there is a system setting somewhere locking the dislogs to the parent window. I’m not a Linux user so I can’t offer much help in that regard.
2 Likes
Yeah, I tried the option to open in the top left, (ps: top right as well) nothing happened.
Another thing: when I open seamly a dialog appears saying: “Failed to lock/sysroot/home/cristiane.var/app/io/seamly2d/config/Seamly2DTeam/seamly2d-pid2.log” What is this? I have no idea… Thanks
1 Like
That has to be an OS thing that’s pinning the dialogs to the center of the main window. I don;t think there’s much I can do about that. For most of the tools though you can use the Property Editor instead of a tool’s dialog. It’s just the spline tools that you have to use the dialogs to edit the nodes & control points.
“seamly2d-pid[xxxx].log” is a (debug) log file created each time you run the app. PID being the app “process identifier”.
Does this happen everytime you run the app?
2 Likes
That has to be an OS thing that’s pinning the dialogs to the center of the main window. I don;t think there’s much I can do about that. For most of the tools though you can use the Property Editor instead of a tool’s dialog. It’s just the spline tools that you have to use the dialogs to edit the nodes & control points.
“seamly2d-pid[xxxx].log” is a (debug) log file created each time you run the app. PID being the app “process identifier”.
Does this happen everytime you run the app?
1 Like
[quote=“Douglas, post:8, topic:12733”] Does this happen everytime you run the app? [/quote]
yes! It does!
Thank you for the explanation! I am in the Endless OS Forum as well, I’ll open a topic about it there, maybe they can fix it! Have a great weekend!
2 Likes
You could try and delete the seamly2d-pid2.log and the lock file seamly2d-pid2.log.locked that is most likey there, and see if that get rid of the warning.
3 Likes