Howdy guys, I had an interesting discussion with Chris Yep this afternoon. Among other things he inquired about the ³set analysis limit² command (Also known as move limit in the Setting/Analysis box). There is some ambiguity between what Chris and I believe is occurring and how this command is documented.
Chris believed the move limit may influence the filtering command because the help says ³Specify the maximum number of possible moves analysed², however when he ran the analysis no matter what he set it to .. Analysis always seemed to take the same time. His question was basically if ³set analysis limit² had any influence on the analsysis (or the filter). At first I told him that I thought it had no influence except on the backend when displaying the best moves (after a move analysis is complete). The code in analsysis.c that uses cAnalysisMoves appears to suggest the same (After the move analsysis the move list is truncated (when the move limit is >=2 ). So this begs the question. If I understand thing correctly maybe the help associated with this command should read something like: ³Specify the number of top moves from an analysis to display² Rather than: ³Specify the maximum number of possible moves analyzed² (This suggests the analysis itself may be influenced by the setting) On the same subject, I am curious about the rationale for a value of 0 and 1 to mean ³unlimited². I would think 0 would be unlimited and a value of 1 should be ³1 move to display². It seems the minimum number to display is 2. I may not know the reason, so I¹m asking :) . After playing a bit with this feature I noticed that there may be a couple of minor glitches. When I use ³set analysis limit 2² and analyze an opening 6-4 the move numbers in the analysis pane are listed as ³1² and ³-1² instead of ³1² and ³2². As well the users move is not highlighted in red (nor does a star appear beside the move number). I have a feeling these are just minor glitches that have crept in over time, liekly suggesting setting ³move limit² to anything other than 2 is not very common at all. Lastly, is this feature very useful at all (It might be to people using the command line and console output?), do people really use it? Candidate for code cleanup/removal? Michael
_______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
