Gian-Carlo Pascutto wrote:
I'm not going to implement this as there is no standard, no specification and no GUI for it. I'm just saying I wish UCI had forseen this.
Fair enough, but I think I've got the picture now. Here is the discussion in a nutshell:
1) Me: Please implement 'searchmoves'
2) Engine authors: We have a better idea which makes 'searchmoves' redundant.
3) Me: Will you then implement it instead of 'searchmoves'
4) Engine authors: No, there is no standard, no specification and no GUI for it.
So, we have a tough situation here.
On one hand 'go window' won't be implemented because there is no standard, no specification and no GUI for it. On the other hand 'searchmoves' won't be implemented, even if it is a part of the UCI standard, it has a specification, there are GUIs supporting it and there engines supporting it. The reason is that 'go window' is a better idea. Continue reading from the start of this paragraph.
Engine authors are clearly a tough crowd, but I wonder if they often talk themselves into a stalemate situation like this.
Because searchmoves is equivalent to feeding the child positions to the engine
OK, here you are encouraging adding this feature to the GUI. In another post you say you don't want to encourage adding new features to Aquarium.
I don't think this discussion is leading anywhere.