[PATCH] Don't re-send CECP engines the last move after a setBoard().

nullx002 / pychess

Automatically exported from code.google.com/p/pychess

GNU General Public License v3.0

1 stars 0 forks source link

[PATCH] Don't re-send CECP engines the last move after a setBoard(). #651

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago

This is a 1-liner.
To reproduce the problem, use "enter game notation" to match pychess vs pychess 
after "1. e4". Pychess gets "usermove e4" twice and dies.

Original issue reported on code.google.com by Uncombed...@gmail.com on 9 Mar 2011 at 7:37

Attachments:

pychess_cecp_setBoard.patch

GoogleCodeExporter commented 8 years ago

Great catch! Wonder how long that bug has been around :O

Original comment by lobais on 9 Mar 2011 at 8:26

Changed state: Fixed

GoogleCodeExporter commented 8 years ago

Issue 400 has been merged into this issue.

Original comment by lobais on 9 Mar 2011 at 9:19