Adding:
if {$::autoplayMode} { return 0 }
at the beginning of the proc ::move::drawVarArrows fix it.
Bye,
Fulvio
Pascal Georges wrote:
Indeed it is broken if the option to show variation arrows is ON. I
looked at the code and could not find its side effect.
Fulvio, could you also have a look ?
Pascal
2009/12/9 Joost 't Hart <joost.t.h...@planet.nl
<mailto:joost.t.h...@planet.nl>>
Pascal Georges wrote:
Fixed. In CVS.
Pascal
Sorry, but it is not fixed (actually, it has become worse).
At the variation point, the analyis goes one move back (instead of
one move forward?).
See attached screen shot.
Start analysis - without book - of 1.e4 e5 2.Nf3 Nc6 3.a4 (3.h4 h6
4.g3) 3... a6 4.b3
At the point where the two arrows for 3.a4 and 3.h4 are displayed,
analysis now resumes at 2... Nf6 (and keeps on resuming there, see
the screen shot).
Thanks,
Joost.
2009/12/7 Joost 't Hart <joost.t.h...@planet.nl
<mailto:joost.t.h...@planet.nl> <mailto:joost.t.h...@planet.nl
<mailto:joost.t.h...@planet.nl>>>
Hi!
Linux, CVS, Tcl/Tk 8.5.7
With auto-annotating a game with variations (deepshredder UCI,
annotate
all moves but NOT variations), annotation is blocked at the
position
with the green/blue arrow on the board. After analysing that
position is
restarts annotating the same position over and over again.
This may have something to do with the double-key-advance
functionality
recently added. The engine (control) is not aware of this
and does not
know how to advance in the game.
Phalanx-scid (non-UCI) does not really survive this
blockade: It
throws
in two completely different variations (and different position
judgements), followed by error messages of the nature
"(Error reading
move: Ng8f6)"
Cheers,
Joost.
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
<mailto:Scid-users@lists.sourceforge.net>
<mailto:Scid-users@lists.sourceforge.net
<mailto:Scid-users@lists.sourceforge.net>>
https://lists.sourceforge.net/lists/listinfo/scid-users
------------------------------------------------------------------------
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
------------------------------------------------------------------------
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
<mailto:Scid-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/scid-users
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
<mailto:Scid-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/scid-users
------------------------------------------------------------------------
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
------------------------------------------------------------------------
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
