well, this is too technical for me, but do I understand correctly that different methods are used to access files, when saving, opening, linking, whatever ... and thus the behaviour is inconsistent: works most of the time, but not always ?wmayer wrote: ↑Mon Aug 31, 2020 12:01 pmWhen loading a project then inside App::DocInfo::get() an entry to a map is added with information about the document. As key the absolute file path with the soft link is used.
When trying to search for the further assembly files while loading the project the function App::DocInfo::restoreDocument() is used. In this function the path was created with QFileInfo::canonicalFilePath() and thus the soft link has been resolved to the real path. This path is used to search in the map but because it has no matching key the second file won't be loaded.
If this is the case, would it be possible to not do any smart magic for v0.19, propose only simple and reliable methods, whatever they are (you will know better than me), and leave room for improvement for v0.20 ? This will not allow all fancy use-cases, but at least will be rock solid and easy to explain/document.