TeslaSpecter

If it's a subjective matter, may I cast my opinion on this; For my workload, I think it would work best if the "save a copy as" used the .pdn parent's project name for the name, then used the last saved format used by "save a copy as" (if that's possible- not sure if windows exposes that or not.) Any other new types of saves, such as "export as" would have their own last extension type and file name remembered for their respective dialogs. Maybe off topic but: Alternatively, for my workload, I would never need anything more than the already implemented "save as" if there wasn't a need to flatten a .pdn before saving as an alternate extension type. I think logically this could be accomplished by the addition of a "save project" button. This would specifically save the .pdn in the place the project was started in the first place. Upon clicking the save button, it would save a flattened image file in the previously used name and extension type. Upon closing a project, it would save the project to the .pdn file (a checkmark saying to "always save project file on closing" would be helpful too.) As for preserving project quality, perhaps it would be good to save the .pdn file when performing a save as. If not all would like this feature, perhaps it could be a checkmark box to not ask in the future. Thank you very much for your time