Comment 6 for bug 1662531

thanks for testing! apologies in advance for the lengthy response:

1. With respect to the File->Save As... dialog not appearing. I wonder if you would be willing to run the prepare_file_save_as extension again, just in case it works the second time. I have a vague memory that I encountered the same problem myself and then it went away. I know that there is a difference between the very first run and subsequent runs, because the default save-as directory is different. The first time I run it, the default directory is the directory of the temporary file, which is quite inappropriate. The second time I run it, it will use whatever directory I used the first time, which is hopefully more accessible. fwiw, I have run this successfully on:
Windows XP, Inkscape 0.92pre4 (32 bit)
Windows 10, Inkscape 0.92.0 r15299 (32 bit)
both of which were 32 bit builds.

2. With respect to the File->Save As..., again, I get a crash with a runtime error dialog when I run it on Windows 10, Inkscape 0.92+devel 15458 (64 bit) trunk. I will investigate that.

3. With respect to adding an option to the existing save as dialog, I am not entirely sure that this would work. The extension relies on the idea that a second instance of Inkscape will be run in order to prevent corruption of the original file, and it is this second instance that calls up the save as dialog, so the first save as dialog is no longer needed in this case.

4. With respect to adding an option to a print_win32_vector dialog, it currently does not have a dialog, it just calls up a printer dialog. I would like to make the original "Win32 Vector Print" extension invisible on the menu, but don't know how to do that. I would very much also like to merge the extensions "Pre-Process Win32 Vector Print" extension with the original "Win32 Vector Print" extension. However I don't know how to do that. When I merge them I end up in an infinite loop which is very difficult to recover from, because one instance of Inkscape is forever calling up a new instance.

I'll report back if I fix the 64 bit crash.