bug-xboard
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-XBoard] [bug #27772] Board and holdings out of sync


From: anonymous
Subject: [Bug-XBoard] [bug #27772] Board and holdings out of sync
Date: Fri, 23 Oct 2009 10:25:28 +0000
User-agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; GTB6; .NET CLR 1.0.3705; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)

Follow-up Comment #6, bug #27772 (project xboard):

Ah, good observation. I guess this tells us how they implemented it on the
server; when a piece is captured they first send a holdings update to the game
that receives it, and after it print the board to the game making the capture,
both in bughouse and crazyhouse. Except that in crazyhouse this is the same
game.

They should have sent the holdings update after sending the board, or
suppress it altogether in crazyhouse.

As it now seems to work with the flag, I will keep it that way for now, and
just keep in mind that there is a better solution for when we are going to do
some code refactoring.

There still will be a problem for the part of the game you have not been
observing. The holdings will be empty for that part, as move lists do not
contain holding updates. In crazyhouse the updates are implied by the moves,
of course. So in principle I could alter the flow of information during ICS
play, and derive holdings (and castling rights in FRC, and info on which
pieces are really promoted Pawns) from the previous position (if known) and
move, rather than from the board sent by the ICS. But that would still not
work in bughouse, so I am not going to bother with that now, and leave it for
a later version.

H.G. Muller

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?27772>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]