[Bug-XBoard] [bug #27642] Clock jumps strangely in engine mode

[anonymous]

Follow-up Comment #4, bug #27642 (project xboard):

OK, thanks for tracing this down. I had gotten as far as concluding that the
first tick after a clock switch was always 1000 ms, rather than the remaining
fractional second on the new side-to-move's clock, and that this was
compensated only on the next tick, but had not found the reason yet.

The problem is that SwitchClock() uses forwardMostMove, so after the 'bare'
patch it was using the time of the wrong player to decide on the tick length.
The proper fix is to move SwitchClocks() and the two timeRemaining-referring
lines behind it to after the forwardMostMove++.

This means that the time for performing the move on the board is now added to
the time of the player that just moved, rather than the player that is going
to move, but this should not really make a difference, as this should be only
micro-seconds.

Again, thanks for spotting the bug, and for locating it!
H.G. Muller

    _______________________________________________________

Reply to this item at:

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

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