Absolutely! The behavior is really inconsistent with the other export or save options.
• Save As > keeps the same directory of the file you are working in
• Export > keeps the same directory of the file you are working in
• Package > starts in the directory of the last file you packaged.
It's really annoying when I have 10 projects that are finalized and approved, and I just need to package them up really quick.
My current workflow to remedy this is to Save As... and then copy the relevant long directory in the file path bar that, then select Package and paste it over the irrelevant directory. It's a few extra clicks but it works.
I can see a workflow where package files exist outside of the working file, but at the very least give a check box option to package in the same directory as the active file.
Gilbert
Absolutely! The behavior is really inconsistent with the other export or save options.
• Save As > keeps the same directory of the file you are working in
• Export > keeps the same directory of the file you are working in
• Package > starts in the directory of the last file you packaged.
It's really annoying when I have 10 projects that are finalized and approved, and I just need to package them up really quick.
My current workflow to remedy this is to Save As... and then copy the relevant long directory in the file path bar that, then select Package and paste it over the irrelevant directory. It's a few extra clicks but it works.
I can see a workflow where package files exist outside of the working file, but at the very least give a check box option to package in the same directory as the active file.