Working Directories - Opening and Saving Files

[dkopacz]

When working in PixInsight I find it frustrating to constantly have to select the same folder repeatedly, especially when working in nested directories.

I prefer to organize my folders according to purpose, rather than renaming files. When I save a file in PixInsight, such as a cropped image into a directory called "Cropped", then save another cropped image, I repeatedly have to browse to the newly created folder. Many other application I work with remember the last folder to which I browsed and remember it for selection the next time I want to save a file.

It would be very nice to have PixInsight remember all of my folder selections for object types. For example, I should be able to set up a Calibration directory and each time I use the ImageCalibration tool it remembers where my calibration directory resides.

When I save a file, then save another after using the same tool, such as the dynamic crop tool, PixInsight should remember where I previously saved a cropped image and automatically open that folder.

You could also take this a step further and have PixInsight read the file name or file header of the object upon which I am working and always open to the directory with the same name. For example, I was just working on an NGC7133 project and every time I opened a file using the File menu, PI would open to my NGC7023 folder? I have no idea why it remembers that folder, but even after browsing to the NGC 7133 folder and selecting an NGC7133 luminance file, upon opening the next NGC7133 file, PI took me right back to the NGC7023 directory.

I would very much like an option that at least recalls the previous directory choice I made and selects that directory as default next time I try to perfrom a similar operation. This way I would only have to browse to a directory once. This should be implemented independently for OPEN and SAVE operations as I usually open a file from one directory, manipulate it and save it in a different directory.

Thanks for reading. I hope to see these changes implemented in a future release.

[cdesselles]

Additionally, I would like to see if filenames could include spaces rather than underscores or dashes.

[bitli]

Or maybe ther open function could call a script with the window or process requesting the opening and the type of file desired, having access of the files already loaded, the history of load and other information, and deciding which file(s) to load or to present to the user for selection and in which format. The default would be a script with the current behavior. Same with save.
I am sure that some of us could come with pretty interesting way to automatically manage the files.
But the documentation first !
-- bitli

[paulcolenbrander]

+1

[martin farmer]

Yes good idea +1 more

[georg.viehoever]

...But the documentation first ! ...

+1