Open luca-della-vedova opened 5 months ago
Is this fixed by #214? Your comment in the PR is that it mostly addresses the issue, but it's not clear to me what else needs to be addressed.
The missing part is that the combination of relative and absolute paths does not work.
This means that if a user was to open a project when using a relative path, for example through:
cargo run --release -- path_to_file.site.ron
Then save it from the UI to a different file, migration between the relative and the absolute path fails and the new paths won't work anymore. Everything else (I believe) works as expected.
When loading a file with relative paths (i.e. drawings) and saving to a different path, the path migration does not quite seem to do what it's supposed to.
I added the following path to
rmf_site_format/asset_source.rs
to show what's happening:Then ran:
And saved to the same folder. The printout was the following:
Note how there is an additional
../
in front of the path, and for this reason the newly saved file is unable to load the drawings. I believe, based on the old and new reference paths, the migrated path should not contain the extra../
since they are in the same folder.