Save Game vs. Save Game As

[Sully]

It has been standard application behavior for decades that Save As prompts for a filename and on a successful write makes that file the current file, while Save writes to the current file without prompting if there is a current file. The change in 3.2.17 is that we made VASSAL follow standard application behavior. There is nothing unusual and should be nothing unexpected about how Save works now.

I think there is a VASSAL bug here. When a game is implicitly (via synch) or explicitly closed VASSAL should clear the name of the last file used so the user is prompted for a new name when they save. -Sully

 

[uckelman]

I'll have a look at this sometime in the coming week.

 

[uckelman]

I've uploaded a build which I believe corrects the problem with a saved game remaining the current file
after it's been closed. The test build is 3.2.18-svn9251, available here:
http://vassalengine.sourceforge.net/builds/
http://vassalengine.sourceforge.net/builds/

Please give it a try and let me know whether this behaves as expected.