Yes - definitely a worthwhile feature.
I have added it to subversion and the windows release candidate
I think this code below is correct, but testing should tell.
Steve
+ spinbox $w.cutoff.spBlunder -width 4 -textvariable annotate(cutoff)
-from 3.0 -to 10.0 -increment .5
proc addAnnotation {} {
....
set deltamove [expr {$score - $prevscore}]
set isBlunder 0
+ ### Don't process if score above cut-off score,
+ # excepting for the case when score goes from -5 to +7 (eg)
+ if {abs($prevscore) < $annotate(cutoff) || (abs($deltamove) >
abs($score) && $score*$prevscore < 0)} {
### Calculate isBlunder
On Wed, Nov 27, 2013 at 10:03 AM, Igor Sosa Mayor
<jos...@gm...> wrote:
> Am Tue, Nov 26, 2013 at 11:04:55AM -0500, John Gray wrote:
>> Hi all. I hope it isn't bad etiquette to make a feature request in one's
>> first post. I would really like to be able to specify a cutoff threshold
>> when doing automated game annotation with an engine. So in addition to
>> defining a blunder as a change in score (e.g. of 100 = 1 pawn), I would
>
> I find this a very useful feature request. I send a patch which could
> achieve this. Maybe it is not perfect. It is the first time I make
> something in tcl...
>
> Cheers.
>
> Igor
>
> --
> :: Igor Sosa Mayor :: jos...@gm... ::
> :: GnuPG: 0x1C1E2890 :: http://www.gnupg.org/ ::
> :: jabberid: rogorido :: ::
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
> _______________________________________________
> Scidvspc-users mailing list
> Sci...@li...
> https://lists.sourceforge.net/lists/listinfo/scidvspc-users
>
|