On Wed 23 Aug 2006 (20:29 +0200), Jim Segrave wrote: > On Wed 23 Aug 2006 (17:44 +0200), Jim Segrave wrote: > > On Wed 23 Aug 2006 (17:39 +0200), Christian Anthon wrote: > > > Sounds like a more educated fix, however, it doesn't quite work: > > > > Nope, I'm working on it. I did a quick hack on a test system (not > > current) and, as luck would have it, it looked normal, but there is > > more setup to be done. I should have it solved in a few minutes. > > Hmm - I'm struggling with this one - CommandRollout is re-using too > many data structures (it was OK when each rollout was done to > completion, but has been wrong ever since - the count of trials and > all the stats were in a common data block for a hint. I'll keep > working on it.
I begin to see something interesting. If you run gnubg with a GUI from an xterm (or, I suppose, a DOS window) and enter the commands Jon posted, you'll get the erroneous results identical to the CLI version - this one calls CommandHint() followed by CommandRollout(). In the GUI if you pop up a Hint window and then select some moves ans ask for them to be rolled out, you get the correct result. In this case, it calls ScoreMoveRollout(). The two routines have much in common, so much so that they need to be merged into a single routine. The logic is fairly complicated, but I think the cause lies in a failure to correctly set up the board and the flags needed for a rollout. -- Jim Segrave [EMAIL PROTECTED] _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
