2009/11/5, f...@libero.it :
>>
>> > So what others think about this : when the user enters a move, if the
>> > move already exists in the main line or in a variation, the move is not
>> >
>> > duplicated but we simply move forward (no need to display the dialog box
>> >
>> > asking for adding a var
f...@libero.it wrote:
Hi!
> There are different ways to enter into variations with scid:
> 1) Using the variations popup window: probabily the best
> way if one use keyboard arrows to navigate in games, but
> it's annoing to always have to confirm that you just want
> to stay in the main line.
>
Pascal Georges wrote:
Hi!
> [Fulvio, I copy Scid users list to see if others agree with our point
> of view]
I fear I can not really follow your discussion here.
> One other comment : in a previous patch, there was some code to
> handle
> the case where a move is enter
> That's right, and that is also my point of view about confusing games. But I
> see an issue here : if a move already exists in several variations, the
> first encountered is entered into. Maybe in that case it would be better to
> fallback to the display of the variation window (or something like
[Fulvio, I copy Scid users list to see if others agree with our point of
view]
2009/10/27 Fulvio
> Pascal Georges wrote:
>
>> One other comment : in a previous patch, there was some code to handle
>> the case where a move is entered and if already existing in a
>> variation, this variation was e
Pascal Georges wrote:
> What do you mean by "should work" ? Did you test it in various cases
> (vars window on/off, docked window on/off) ?
I wrote last e-mail from a pc without a compiler.
This is the correct complete changelog:
Index: tcl/end.tcl
What do you mean by "should work" ? Did you test it in various cases (vars
window on/off, docked window on/off) ?
Pascal
2009/10/6 Fulvio
> Pascal Georges wrote:
> > The idea is nice but there are a few problems :
> > - right now it does only make sense when "show variations window" is
> > turn
Pascal Georges wrote:
> The idea is nice but there are a few problems :
> - right now it does only make sense when "show variations window" is
> turned off. Hence it should be better integrated with this : either
> they are mutually exclusive or combined
> - when going back, the arrows displaying
The idea is nice but there are a few problems :
- right now it does only make sense when "show variations window" is turned
off. Hence it should be better integrated with this : either they are
mutually exclusive or combined
- when going back, the arrows displaying possible vars for current move is
I wrote some code that improves (i hope) the behavior of mousewhell
scroll over the board:
1) Scrolling back automatically leaves a variation
2) Scrolling forward shows arrows indicating moves for multiple variations
Would you give it a try?
Index: src/tkscid.cpp
===
10 matches
Mail list logo
