Comment 4 for bug 1191156

Thanks for the idea. Part of the problem is Windows and it's constantly changing behavior. v0.6 and earlier used getSaveFileName() and didn't have any issues. With Windows 7, if the file selected existed AND was read-only, the dialog would fail. When fixing this and adding features to v0.7, I switched to getOpenFileName() and added a comment in the readme about the change and the (temporary) work around for saving a new file (just type in the filename and click read, the program will write a new image file in your %USER%/Downloads directory (which can now be overridden with %DiskImageDir% in v0.8).

I am looking into a generic file selection option, or the ability to add a button to the Open File dialog to create a new file (similar to the New Directory button).

I do like your solution and will give it a lot of consideration. Main thing is I want to get something working before the end of June, so I can push another release that also fixes lp:1118217 (another fine example of Windows API changes).