Import capability for library elements
Placeholder for the case that libraries are fully supported again.
The current import code for AF3 Projects scans for libraries in the
source directory and copies them to the import location. Thereby, the
code overwrites existing libraries.
Consequently, the code risks data loss! Thus, in the ticket #3993 (closed), the import of libraries will be removed.
In order to properly support importing of AF3 Projects with library elements, the following approach must be taken:
- Check if elements from a library are referenced.
- If so, check if a library exists in the target location.
- If not, create one.
- Add each referenced element from the source library to the target library.
- If an equivalently named and scoped element exists in the target directory, error-out or offer some handling to the user.
NOTE, that this logic must be executed BEFORE the project file is copied to the target directory to maintain the references when the kernel performs the actual import.
(from redmine: issue id 3996, created on 2020-04-09)