MultiPV adjustment in Hints panel not discoverable

[GoogleCodeExporter]

I didn't even realize you adjusted MultiPV by clicking the "1" next to the 
engine analyzer name in the Hints panel until reading the code in bookPanel.py. 
Previously, I'd thought you did it by editing the UCI options in the Engines 
editor dialog. Maybe if/when we split up the Hints panel into 3 separate 
panels, this control could be made more obvious by putting it into an "Engine 
Controls" section with other things like the move search time (which is now in 
the Preferences dialog) and maybe a "Pin analysis to shown position" option.

Original issue reported on code.google.com by mattgatto on 4 May 2014 at 9:29

• Blocked on: #860

[GoogleCodeExporter]

The "Engine Controls" section I mentioned would go into the split-out Engine 
Analysis panel, which would have the controls and the actual analysis from the 
engine. The attached images (Fritz 13) has controls for, cpu #, adjusting 
MultiPV (I think), and stopping the engine. They also have labels showing kN/s, 
depth, best move eval, and time spent analyzing move.

Original comment by mattgatto on 4 May 2014 at 10:03

Attachments:

• fritz13-20.jpg
• fritz13-13.jpg

[GoogleCodeExporter]

The Crafty Chess gui has a Ponder checkbox, and a Strength slider adjustment, 
which would be good too.

However, all the rest of the stuff in its "Crafty Control Panel", like changing 
the side/color the engine is playing, and the time controls, should, I think, 
go in a different dialog, available from the Game menu, such as "Game 
Settings", that is a subclass or related class of the New Game dialog. Or make 
it a combination of New Game dialog controls and what's currently in 
Game->Properties.

Original comment by mattgatto on 4 May 2014 at 10:15

Attachments:

• Crafty-Chess.gif

[GoogleCodeExporter]

Unfortunately it's gtk behavior that spin cell renderer shows the control only 
when you click into it. Unless it only shows the value in it.

Original comment by gbtami on 5 May 2014 at 8:09

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

OK, well I guess it needs to be presented in a way that shows that it's an 
editable value, i.e., have something like "Number of variations: " to the left 
of it.

Original comment by mattgatto on 7 May 2014 at 12:25