Re: [Bug-gnubg] Autosave questions

[Massimiliano Maini]

This is how I would make it:

1. If autosaving from a loaded file (eg <file>.sgf), use something like
<file>.0001.autosave.sgf, in the same dir. The 0001 part of the file
name can be used to ensure the file is unique (proper to the current
instance of gnubg). If <file>.0001.autosave.sgf already exists, use
<file>.0002.autosave.sgf: the higher the number, the most recent
the autosave (I means across different instances of gnubg or different
runs of rollouts with autosave).

2. If autosaving without a filename, prompt for one.

3. At the end of the rollout(s), the autosaved file could be deleted
since it is (normally) no longer necessary. Not seeing an autosave
file implies everything went OK. Maybe we could make this optional,
with an option like "Save results once rollouts are done" when
doing a CMark rollout.

MaX.

P.S.
The Analyse/Rollout (I mean the 2nd one, the one for Cmarked moves)
should probably be renamed to Rollout CMarked (or whatever we chose
instead of CMarked).