Not Considering

We are not considering this for now seeing the comments, and also we have added many different ways of working over the years around this in the package flow that we consider sufficient for now. Also when you use the option not to use the project folder, then the last remembered location will always be used so it already works at least partially as intended.

When importing Studio package, make the folder where the package file is located the default project folder

When importing a Studio package, I suggest that the folder where the package file is located is used as the default project folder in the Import Studio Package window (or that it is made possible to choose this behaviour in a setting). I always place the Studio package in the main folder for a given job, and this is also where I want Studio's working directory for the project to be placed. This suggestion would make that easier.

The same directory should also be the default directory for saving the return package. The way it is now, Studio remembers the last folder where a return package was saved, which for me is always the project folder for the previous job I finished. By making Studio use the folder from where the Studio package was opened as default both as working directory for the job and as location for the return package, the whole process of setting up a project based on a package and finishing it would be simplified.

Parents Comment Children
No Data