On 11/27/2015 12:33 AM, f...@libero.it wrote:
>> In the old days (once long ago) the comment editor "cursor" could be
>> "before" and "after" the current move. So creating something like
>>
>> { The game starts } 1. e4 ( { Hm, I would have expected } 1. c4 { from
>> this guy } )
>>
>> was perfectly possible. And importing this stuff should simply work as
>> expected, I would say.
> Hi,
> a comment editor "cursor", as far as I know, do not exist in Scid :)
It was a "cursor" (including the "'s :) )
I name it like that because I seem to remember that the <arrow> actually
changed the colour of the current move "cursor"in the game/pgn window.
> Once upon a time going back one move from the beginning of a variation did
> not
> automatically returned to the main line, and it generated many confusing
> behaviors.
You are right. But I got the hang of it and it worked for me.
> The example above can be create (and imported from PGN) in current Scid.
> This is the sequence to type on the keyboard:
> <ctrl+n><ctrl+e>The game starts<ctrl+e>e4<left-arrow><ctrl+a><ctrl+e>Hm, I
> would have expected<ctrl+e>c4<ctrl+e>from this guy<ctrl+e>
Aha! Well I probably must have used such key sequence an awful lot of
times then.
>
> Gerd's point is different, the problem is that the PGN "standard" do not
> forbid:
> 1. e4 { comment to e4 } { comment to what? } { is this a comment before e5? }
> e5
>
> but if we (really?) want to have a serious discussion about this we need a
> list of how the other chess software (commercial and open) import the above
> PGN.
>
> I personally like to comment _positions_ not _moves_.
I do agree. But I used scid a lot of times in the past to create
readable printed annotations for my club magazine. And there these
tricks are very nice. I have to agree to the OP (pwatts) here. None of
the commercial progs could deliver such pretty output! Not sure about
how this is today.
> Even if I think about people around a concrete chessboard, they talk about
> the
> current position or the position that appears after a move.
> However, in Scid is also possible to comment a variation instead of a
> position
> (but why?) with the hidden <ctrl+a> that creates an empty variation: enter a
> comment before making the move to have a "comment before a move".
I just explained, I hope. The shortcuts are maybe a bit hidden.
Cheers,
Joost.
>
> Bye,
> Fulvio
>
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
