Winboard: Resigning?
Posted: Tue Jun 27, 2017 6:21 pm
Hi,
right now, my engine transmits "resign" before doing the last move, which is as per https://www.gnu.org/software/xboard/engine-intf.html :
However, it seems I'm running into problems with the next game. Here the debug log from Arena. For the next game, "move now" doesn't work:
This is nonsense, the engine isn't calculating. It does not have ponder, and it reacts to ping, so it is ready to receive commands. If I give a "go" manually, it works:
I might also have a similar issue with Winboard 4.8.0, but I'm not sure because there is no debug Window, and ctrl-alt-f12 doesn't seem to do anything useful.
Is the Winboard protocol note misleading in that there must not be any move after resign? Or is it a GUI problem?
right now, my engine transmits "resign" before doing the last move, which is as per https://www.gnu.org/software/xboard/engine-intf.html :
The idea is that this allows GUIs to override resigns in case the user wants to play until mate.Note that many interfaces work more smoothly if you resign before you move.
However, it seems I'm running into problems with the next game. Here the debug log from Arena. For the next game, "move now" doesn't work:
Code: Select all
2017-06-27 17:54:08,541<--1:resign
2017-06-27 17:54:08,541*1*black resigns detected...
2017-06-27 17:54:08,559<--1:move f7g7
2017-06-27 17:54:08,559*1*Found move:Kf7-g7
2017-06-27 17:54:37,653**----------New game---2017-06-27 17:54:37,653 Di -------------
2017-06-27 17:54:37,653-->1:st 10
2017-06-27 17:54:37,654-->1:new
2017-06-27 17:54:37,654-->1:st 10
2017-06-27 17:54:37,663-->1:post
2017-06-27 17:54:37,665-->1:ping 15
2017-06-27 17:54:37,733<--1:pong 15
2017-06-27 17:54:41,912*1*
2017-06-27 17:54:41,912*1*
2017-06-27 17:54:41,913*1*Engine already calculating!
2017-06-27 17:54:41,913*1*
2017-06-27 17:54:41,913*1*
Code: Select all
2017-06-27 17:54:49,698-->1:go
2017-06-27 17:54:49,702<--1:move g1f3
Is the Winboard protocol note misleading in that there must not be any move after resign? Or is it a GUI problem?