Comment 7 for bug 1100228

Actually, this is a change in function due to the Windows File dialog issue. There are two file dialog methods; open & save. The program used to use the save function, which is why it worked when the file didn't exist.

Starting with Windows 7 however, this dialog will fail if the file exists AND is read-only. Switching to the Open method fixes that issue, but now the file must exist or it will fail (as you've seen). My solution to this was to allow the user to type a filename into the file window and if it doesn't exist the program will do the right thing. To reduce confusion on where the program will save new files, and to plan ahead for when we do a proper installation, I added a routine to find and set the default directory to the user's "Downloads" directory. This needs to be fine tuned, but works.

All of this was documented in the readme.

Ultimately, the real problem is that we need a generic file dialog, not an either/or (which is what we have available now). I will look into a better solution for the next release, but I wanted a working solution so that I could get this out.