Hi all,

I simplified the triggering logic (for the GUI to apply the engine move) and made it more compliant with some UCI engines using internal books. Also, I made sure all the PV lines before bestmove sent by the engine were displayed by the SlowWrapper.

As I used the reported depth for halting the display and actually send the bestmove data to the GUI, sometimes additional PVs still at same target depth could be lacking on display, whilst the engine had considered these before reporting its bestmove. There was no impact on the game, yet now the display on the GUI is more reliable, always complete as the engine did report.

New version (v4) attached. Don't forget to adapt the engine exe file name, and the depth_limit and info_delay you want. By the way, info_delay in seconds can use decimals (eg 0.05 would be 50ms - even if such a low value would not help much slowing the engine down).

Regards,
Tibono

ps: new release v4.1, please see hereunder.