Hello, I'm trying to modify my copy of Scid to stop annotating each move when it reaches a depth of 13. i.e. I want to give it a large "time between moves in seconds", say 999, but let it go on to the next move when it reaches a depth of 13.
There are surprisingly few programs which allow that kind of depth-based annotation, a notable exception being chesstempo.com's java-web-based control of your local engine. A novel idea. But that's kind of a pain (e.g. it doesn't check an opening book for the first few moves like Scid does) and I'd like to do everything in my beloved Scid (Mac). As an initial hack, I modified Engine::Think to use an instance variable, depthCounter, to keep track of the current depth, and then added a check for depthCounter >= 13 to Engine::OutOfTime(). However the annotating still carries on merrily past my depth of 13. I think I'm not understanding how the annotation works. Can anyone point me in the right direction? Cheers, Steve ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ Scid-users mailing list Scid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/scid-users
