That's a major fault.
I've tested some of my older files and got tons of broken ones
Usually I saved font files in the same folder as FCStd file accessing with
This is correct. I did not know I was walking us all into a shitstorm when I did this. I tested in GNU/Linux using the snap release and it worked, so I shipped. I'll add a note to the README with a link to the bug.
Agreed. Let's close this discussion with the following conclusion: We'll keep relative paths as they will likely work in future and non-relative paths will be broken for everybody but the original designer anyway.
Amazing. Thanks for this, openBrain.openBrain wrote: ↑Thu Aug 29, 2019 9:59 amIn case it may be helpful to somebody, here how I "check" my FreeCAD models once done :
- Open the .OBJ file of the original object as alias mesh and go to Part WB
- Convert it to shape with Part -> Create shape from mesh
- Convert shape to solid with Part -> Convert to solid
- Refine the solid with Part -> Create a copy -> Refine shape
- Align the refined solid with the FreeCAD model using the Aligner tools of the Manipulator WB
- Use Inspection WB / Inspection -> Visual inspection. Select as "actual" the FreeCAD model and as "nominal" the refined solid. You can change the search range later in the property editor, starting with 100 or 200 µm is generally good.
When using relative paths then the absolute path can be obtained with the application's "current working directory" + "relative path". Usually the current working directory is not set to the path where a project file resides so that the computed absolute path points to a non-existing file.
This kind of reediting manually is necessary if you try to move your FCStd file and corresponding stuff like tff files, which are refereed by your FCStd but are not included, to your team mate on a separate machine.