Re: Scid vs. PC 4.14
Posted: Sun May 24, 2015 9:03 pm
Very stange this. You could also try ChessX or Xboard.
ALL Linux programs that are supposed to be a cinch are not with these UCI engines. I looked at Xboard, u have to compile the damn thing and I looked at it and it wadsn't just a simple ./comfigureCositasBuenas wrote:Very stange this. You could also try ChessX or Xboard.
Nope. He should get iOS.CositasBuenas wrote:Sounds like you need an OS like Android where you simply tap the screen to get what you want. Everything else seems to lead to mental overload.
The word better is, and playable, is dependent on the score difference of the move evals. So if it may happen that the 2nd pv is worst, say -0.15/14, perhpas the output would be.(Better is 9.Nf4 ... +0.28/14)
(Also playable is 9.Bd2 ... +0.19/14)
This would warn the user even without looking at the eval score. The idea is that the user is informed that there is also dangerous move in this position, by playing thru that line the user will get an idea of what will make his position vulnerable. If indeed the 2nd pv will bring the score to negative, and the first pv is positive then I plan to increase the default analysis time of the analyzing engine, say 3x especially when the best pv is not an easy move like recapture. I thought of recording the complexity value of every position so that whenever the engine changes its best pv move more than once, it would be a candidate for increasing the analysis time.(A mistake is 9.b3 ... -0.15/14)
That's an option, but there should be some indication about the search ending. When you enable "fast and slow mode", the stats are updated when "fast" search concludes, but if they don't differ from the final ones (in a noticeable way), there's no other way to know, that the job's done. You could use an italic font, by default, for the provisional stats the fast search produces, and reinstate the active font when the slow search finishes.stevenaaus wrote:Maybe remove the tree progress bar for OS X.
Ok. It's very likely the solution will be an option to hide the tree progress bar.That's an option, but there should be some indication about the search ending. When you enable "fast and slow mode", the stats are updated when "fast" search concludes, but if they don't differ from the final ones (in a noticeable way), there's no other way to know, that the job's done. You could use an italic font, by default, for the provisional stats the fast search produces, and reinstate the active font when the slow search finishes.
Code: Select all
--- tcl/windows/tree.tcl (revision 2342)
+++ tcl/windows/tree.tcl (working copy)
@@ -208,7 +208,6 @@
# pack $w.status -side bottom -fill x
pack [frame $w.buttons -relief sunken] -side bottom -fill x -pady 5
- pack $w.progress -side bottom
pack $w.f -side top -expand 1 -fill both
button $w.buttons.best -image b_list -command "::tree::toggleBest $baseNumber"