#131 Remove->Previous moves should be smarter

[Bruno Rizzuti]

Applying Remove->Previous moves to 1. e4 e5 2. f4 (2. Nf3) in correspondence with 2. f4, it unnecessarily deletes also the variation 2. Nf3. Same if it is applied to 2. Nf3, it turns the variation into mainline and unnecessarily deletes 2. f4.

More generally, it would be better if Remove->Previous moves is available only for mainline. Also, deleting previous moves should be always accompanied by the creation of a FEN reproducing the position that corresponds to the moves deleted.

[Michal Rudolf]

Agreed, the first one is a bug. As for limiting the function to the mainline, I am not sure. I myself use it also for variation, to copy a position from analysis into my training database.

[Bruno Rizzuti]

Now it is different, but again buggy:

1. e4 e5 2. f4 (2. Nf3)

With 2. Nf3 selected, "remove previous move" leads to:

2. Nf3 (2. Nf3)

[Bruno Rizzuti]

Now is back as in the original report. Not very smart, yet... ;)

[Jens Nissen]

The bug has been fixed in SVN.