Share

ChessX

Tracker: Bugs

5 Remove->Previous moves should be smarter - ID: 2872974
Last Update: Comment added ( b_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.


Bruno Rizzuti ( b_rizzuti ) - 2009-10-05 15:04

5

Open

Accepted

Michal Rudolf

Database

None

Public


Comments ( 3 )




Date: 2009-10-11 09:46
Sender: b_rizzuti

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




Date: 2009-10-08 14:14
Sender: b_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)



Date: 2009-10-07 07:35
Sender: mrudolfProject Admin

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.


Log in to comment.

Attached File

No Files Currently Attached

Changes ( 2 )

Field Old Value Date By
resolution_id None 2009-10-07 07:35 mrudolf
category_id None 2009-10-07 07:35 mrudolf