I invite you to download the attachment included in it and try the tool yourself, and then answer some questions regarding the feature implementation of the Project Utility tool's mechanisms.
- The resulted project is ALWAYS called "project", regardless of its original name.
- The resulted project has .fcstd as a file extension instead of .FCStd .
- You can't unpack a file containing an .FCStd dependency, as it gives an error despite the .FCStd present in destination folder:
image
- You can't automate multiple actions without Pythoning.
- You can't delete a failed project.fcstd repack despite having every document closed in FC, resorting in FC closure.
Have you ever used this tool with multiple documents, just like my case? Do you propose some changes to meet particular requirements, or do you agree with mines?