How to deal with multiple game files for the same puzzle?

[GoogleCodeExporter]

A user can save the same game multiple times. Should we ask a user to overwrite 
an existing game file in case a save file already exists? It shouldn't be 
obligatory as sometimes it can be useful to have multiple saves.

To determine the uniqueness of a puzzle we need to calculate a hask key 
consisting of: game seed + gridsize + revision of mathdoku used to generate the 
puzzle. For old game files which do not include the game seed, we can calculate 
a hash key for the grid including following information:
 * cellnumber, correct value, cage the cell belongs to
 * cagenumber, cage solution/operator

Original issue reported on code.google.com by paul.din...@gmail.com on 15 Mar 2013 at 6:03

[GoogleCodeExporter]

Original comment by paul.din...@gmail.com on 17 Mar 2013 at 11:34

• Added labels: Milestone-2.0

[GoogleCodeExporter]

Alternatively we should just remove a save file once restored. I dont really 
see a reason to keep a save file around. Terminology can then be changed to 
"continue" a game rather than "open" a game which makes the behaviour clearer.

Original comment by bbux...@gmail.com on 2 Apr 2013 at 9:37

[GoogleCodeExporter]

Yeah that is possible,

The usage log in version 1.96 gathers information about the number of unique 
games that have been stored and the total number of games files stored. Ideally 
these numbers should be more or less the same. In case a big difference exists 
we should ask the user why and how this is used.

Original comment by paul.din...@gmail.com on 3 Apr 2013 at 3:11

[GoogleCodeExporter]

As of revision 276 it is no longer possible for a user to have multiple saves 
for the same grid.

Original comment by paul.din...@gmail.com on 27 Apr 2013 at 7:29

• Changed state: Fixed

[GoogleCodeExporter]

Unfortunately the issue has not been verified explicitly by an independent 
tester.

Original comment by paul.din...@gmail.com on 8 Sep 2013 at 10:48

• Changed state: Verified