Static Working Directory

Hi Reginald @regpratt,

Thank you very much for sharing your request.

Actually, I think there is some confusion here about how things actually work.

The Working Directory once set, is static, it does not change when you load frames like masters from different folders. I always keep my masters and integrations in separate folders, like I do also with lights, darks, flats etc...

So if you set the working directory to the folder where your lights are, and then load masters from a different folder or even a different drive, then the Working Directory is not changed at all, it still points to the folder of your lights. 

When saving calibrated lights, registered, normalized files, there is a button to overrule the save directory. If you do not overrule it, it will always save in the static Working Directory. Same applies for your integrations/stacks. If you do not overrule with the Set Save Directory, button the results should be saved in the static working directory unless you overrule it yourself.

Does this make sense, can you double check the behaviour and let me know if all is okay or not?

Mabula

So I double checked and what was happening is that after loading files from a different directly, if you then click the working directory button Windows explorer opens up to the last folder from which you loaded files, not the original working directory I set. I always took that to mean if I continued with the workflow that last directly is where the stacks would save. However, I just ran a test stack and you are correct, the stacks did save to the original working directory even though that's not what comes up if I click the working directly button or any of the override buttons. Thanks for clearing this up!

Hi Reginald @regpratt,

Thanks for your feedback. Yes, this is the expected behaviour actually 😉 the working directory is static, but any new file chooser that is opened will open in the last location that was used in the file/directory chooser.

Mabula