On Sat, Mar 07, 2020 at 03:08:25PM +0000, Ian Shaw wrote: > Gnubg wipes out previous games when changing the player name. > > During the second game of a match, I realised that the player names > were as set during a previous session. I edited the name of player 0 > to 'gnubg', and the records of the proves game was wiped out. The > current game became game 1, although the score remained the same.
Since changing the player name through Settings / Players doesn't take effect immediately, I suppose you used Edit / Edit position. This indeed creates a new session starting from the position at hand + edits, clobbering the current session, and without warning. The first part may be unintuitive and the second is clearly bad. > This must surely be undesirable, especially with no warning given. > Shouldn't we keep the games played and just change the name? Doing things differently depending on whether the editing is harmless (like changing a name) or not might be tricky Clarifying what "Edit position" does is probably needed in any case, or redefinig what it should do if the current behaviour is inadequate. For the problem at hand, being able to change the names in File / Match information could work as well. > I suggest that the player 0 automatically be set to a standard name > when starting a match/session against gnubg. E.g 'Gnubg 0-ply'. This is almost what Settings / Players does.
