marojodk wrote:
Hi!
>> - Open comment editor and place your comment (Ctrl-E)
>> - Press store...
>>
> I think I already tried this, but either I'm doing it
> wrong, or it doesn't work. Say, two possible moves are
> 30.Ke5 and 30.Kf5. When I add a comment before 30.Ke5, it
> shows up fine. However
Michal Rudolf wrote:
Hi!
>>> Previously it was, so it is only the question of not
>>> blocking all NAGs in GUI.
>> Hm. Could try if that works.
> Not a long time ago it was possible to enter variation,
> take first move back and insert NAG. In fact, as only
> post-move NAGs were supported by Scid
Thanks for your reply! Some additional comments in the text:
Alexander Wagner wrote:
> maroj...@netscape.net wrote:
>
> Hi!
>
>> 1. Adding comments in front of a move. This is very useful
>> for comments like "The idea is Ng3" of "Worse is Bb6
>> because of". Be aware that the same effect cannot b
Alexander Wagner, niedziela, 22 marca 2009:
>> Previously it was, so it is only the question of not
>> blocking all NAGs in GUI.
>Hm. Could try if that works.
Not a long time ago it was possible to enter variation, take first move back
and insert NAG. In fact, as only post-move NAGs were support
Michal Rudolf wrote:
Hi!
>>"->",// $40 White has the attack (DR: ->)
>>"->",// $41 Black has the attack (DR: ->)
>> Clearly, $40 is different from $41, how to express this
>> in symbols? (The problem is the same in UTF.) An idea
>> would be to pre/append a + for white a - for blac
Alexander Wagner, niedziela, 22 marca 2009:
>There is another open point. How to deal with these type of
>NAGS:
>"->",// $40 White has the attack (DR: ->)
>"->",// $41 Black has the attack (DR: ->)
>Clearly, $40 is different from $41, how to express this in
>symbols? (The problem i
Michal Rudolf wrote:
Hi!
[7-bit table]
> Many NAGs are present in most Unicode-enabled fonts,
Sure. All of them should actually exist, many of them being
well established symbols in math.
> including freely available corefonts. Maybe we can provide
> alternative version using these characters:
Alexander Wagner, niedziela, 22 marca 2009:
>maroj...@netscape.net wrote:
>
>Hi!
>
>> 2. Graphical annotation symbols. Maybe it's just me, but
>> I'm hopeless at remembering $22 or $23 or strings similar
>> to that. It doesn't compare to a zugzwang symbol. Although
>> I agree that in general using
maroj...@netscape.net wrote:
Hi!
> 2. Graphical annotation symbols. Maybe it's just me, but
> I'm hopeless at remembering $22 or $23 or strings similar
> to that. It doesn't compare to a zugzwang symbol. Although
> I agree that in general using text instead of annotation
> symbols is to be prefer
I get the same behaviour on Mac, focus doesn't follow the mouse.
Israel
On Mar 21, 2009, at 2:22 PM, Chris Lott wrote:
> On Sat, Mar 21, 2009 at 10:48 AM, Alexander Wagner
> wrote:
>>
>> Could it be that there is a missundersanding? Focus follows
>> mouse is a very common feature on Unix, but I
On Sat, Mar 21, 2009 at 10:48 AM, Alexander Wagner
wrote:
>
> Could it be that there is a missundersanding? Focus follows
> mouse is a very common feature on Unix, but I don't think it
> is generally known concept on Mac or Windows, possibliy
> giving a usability problem there. I love it and use i
maroj...@netscape.net wrote:
Hi!
> 1. Adding comments in front of a move. This is very useful
> for comments like "The idea is Ng3" of "Worse is Bb6
> because of". Be aware that the same effect cannot be
> achieved by adding a comment after the previous move!
This is possible, however it might b
Hey,
I've been following the posts on the mailing list for some time, and I thought
I'dd add my two cents to try and help to improve Scid even further. Mostly,
generic Scid is excellent. Almost everything is possible, it's just not that
easy to see how. Therefor, I think it's a fabulous idea to
13 matches
Mail list logo
