From 4ef3f26373903d56688ab2ffde7bbb3481f2be4c Mon Sep 17 00:00:00 2001 From: H.G.Muller Date: Sun, 8 May 2016 20:04:36 +0200 Subject: [PATCH] Describe use of blue highlights in protocol specs The function of 'blue' markers, and the role of the 'choice' command in this is explained in the CECP specs. --- engine-intf.html | 10 ++++++++-- 1 files changed, 8 insertions(+), 2 deletions(-) diff --git a/engine-intf.html b/engine-intf.html index bc4815f..b8b09fb 100644 --- a/engine-intf.html +++ b/engine-intf.html @@ -1853,8 +1853,9 @@ Some colors have special meaning to the GUI: - - + + +
colorused foreffect
redcapturehovering over the square makes the GUI send a "hover" command
magentapromotionmoving to the square will be treated by the GUI as a promotion
cyanmulti-movemoving to the square will not complete the move entry
magentapromotion choicemoving to the square will be treated by the GUI as a promotion
blueforced promotionmoving to the square will automatically promote the piece as specified in a 'choice' command
cyanmulti-leg movingmoving to the square will not complete the move entry
greenvictimsno real effect, but used by convention to indicate capture victims on "hover"
The GUI will use the markers for legality checking, @@ -1875,6 +1876,11 @@ to alter the choice offered to the user for the promotion piece from what the GU to the piece IDs mentioned in the PIECESTRING. The IDs in that string should be given as capitals irrespective of color. The first piece mentioned will be the default choice. +An engine must send this command on receiving a 'put' on a square that it highlighted in blue, +or the move will not be completed; +the GUI must wait for the 'choice' command in this case, +to complete the move with the specified promotion suffix, +which will then always be the first piece mentioned in the PIECESTRING. -- 1.7.0.4