Similar to APC files, it would be much more convenient if Autopipe packaged all essential sub files during an analysis project and created a single file by default. It would ensure that the user does not make a mistake and stores the wrong files. In addition, provide a cleaner UX to the user. Especially, if multiple iterations of a model are created.
Hi Sujaan, this is an automatic status for something that is there either in part or fully. The only other option was Will not Implement. I still believe the vast majority will want separate files because of the flexibility. APC provide an archive option and most users and using APC to archive finished models and combine input and output files.
Hi Phil, your classification that this functionality already exists is incorrect.
By default, Autopipe creates 15-20 files as I have stated. While some users may prefer having separate files, the purpose of this idea is to highlight the need to have a single file format that encapsulates all the sub working files Autopipe creates.
Similar to docx, xlsx, xmcd, F3D, dgn etc. One working file that contains all the required information.
This does not already exist. APC is an additional process and file format that is not the base working file format of Autopipe. Users need to remember to recreate an APC file if changes are made to the Autopipe model. A more robust process would be to allow the user to choose if they would prefer working with one file, or 15-20 files using a setting.
The APC file is the convenient way to package this and it already exists. Keeping the loading files separate means they can be used by multiple models, which is generally more convenient to most users. Multiple iterations of a model do not exist unless the user saves them. I believe with the Open Recent, Model Preview and APC we have adequate model handling control.
This doesn't already exist. By default, Autopipe creates 10-15 files.