Pascal Georges wrote:
2009/12/4 Fulvio mailto:f...@libero.it>>
Pascal Georges wrote:
2009/12/2 Fulvio mailto:f...@libero.it>>
Pascal Georges wrote:
>> Many tricks are used in code to try to fix it: temporarily
disabling,
>> erasing the comment window
2009/12/4 Fulvio
> Pascal Georges wrote:
>
>
>
> 2009/12/2 Fulvio
>
>> Pascal Georges wrote:
>> >> Many tricks are used in code to try to fix it: temporarily disabling,
>> >> erasing the comment window text to avoid duplication, etc...
>> >> But in my opinion it's a design error: preMoveCommand
Pascal Georges wrote:
2009/12/2 Fulvio mailto:f...@libero.it>>
Pascal Georges wrote:
>> Many tricks are used in code to try to fix it: temporarily
disabling,
>> erasing the comment window text to avoid duplication, etc...
>> But in my opinion it's a design error: preMoveCom
Commendable teamwork!
--
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.
2009/12/2 Fulvio
> Pascal Georges wrote:
> >> Many tricks are used in code to try to fix it: temporarily disabling,
> >> erasing the comment window text to avoid duplication, etc...
> >> But in my opinion it's a design error: preMoveCommand and every
> >> reference to it should be deleted.
> >>
>
Pascal Georges wrote:
>> Many tricks are used in code to try to fix it: temporarily disabling,
>> erasing the comment window text to avoid duplication, etc...
>> But in my opinion it's a design error: preMoveCommand and every
>> reference to it should be deleted.
>>
>
> "preMoveCommand" is ind
2009/11/30, Fulvio :
> Ok, I replicated the problem (sort of).
> 1) New game
> 2) Make move 1. e4
> 3) Open the comment window
> 4) Write a comment and store it
> 5) Make another move 1... e5
> 6) The comment is still there
> 7) Go back to move 1. e4
> 8) Make another move 1... c5 and select add n
Joost 't Hart wrote:
Fulvio wrote:
Girolamo Castaldo wrote:
This time, it's still there.
In file main.tcl can you try to comment line 1271:
if {[winfo exists .commentWin]} { .commentWin.cf.text delete 0.0 end }
and see if it solves the original problem?
Ju
Fulvio wrote:
> Girolamo Castaldo wrote:
>
>> This time, it's still there.
>>
>>
>>
> In file main.tcl can you try to comment line 1271:
> if {[winfo exists .commentWin]} { .commentWin.cf.text delete 0.0 end }
>
> and see if it solves the original problem?
>
Just tried: the problem i
I've downloaded the binary version, so I'm afraid I can't try that.
Maybe someone else?
-[ Received Mail Content ]--
Subject : Re: [Scid-users] The comment vanishes
Date : Mon, 30 Nov 2009 11:38:47 +0100
From : Fulvio
To : Girolamo Castaldo
Girolamo Castaldo wrote:
> This time, it's still there.
>
>
In file main.tcl can you try to comment line 1271:
if {[winfo exists .commentWin]} { .commentWin.cf.text delete 0.0 end }
and see if it solves the original problem?
-
This time, it's still there.
-[ Received Mail Content ]--
Subject : Re: [Scid-users] The comment vanishes
Date : Mon, 30 Nov 2009 09:49:45 +0100
From : Fulvio
To : Girolamo Castaldo
Cc : scid-users@lists.sourceforge.net
Girolamo Castaldo wrote:
> Ok,
If you close after store it is ok.
- Original Message -
From: "Fulvio"
To: "Girolamo Castaldo"
Cc:
Sent: Monday, November 30, 2009 7:49 PM
Subject: Re: [Scid-users] The comment vanishes
> Girolamo Castaldo wrote:
>> Ok, let's go step by step.
>
Girolamo Castaldo wrote:
> Ok, let's go step by step.
>
> Case 1:
> 1) Create a new game and make a move (eg. 1.e4);
> 2) Add a comment to it and store it;
> 3) Make Black's move (eg. 1...c5);
> 4) Go back to White's move (1.e4): the comment has disappeared.
>
Can you make a test?
1) Open the t
I already have Tcl/Tk 8.5.7, Pascal.
-[ Received Mail Content ]--
Subject : Re: [Scid-users] The comment vanishes
Date : Sat, 28 Nov 2009 23:17:54 +0100
From : Pascal Georges
Cc : scid-users@lists.sourceforge.net
2009/11/28 Girolamo Castaldo
> Yes, the prob
> > So anybody able to see this bug with current CVS ?
>
> As in my previous post: I do!!
The new undo code in CVS seems to have fixed it for me with fedora 7.
Before hand it as 100% reproducible in windows and linux. Here's the
debugging i did anyway, and a tcl hack to get around the issue is a
Pascal Georges wrote:
>
>
> 2009/11/28 Remco Gerlich mailto:re...@gerlich.nl>>
>
> Pascal,
>
> On Sep 7 I reported the same problem (the subject was "Apparent
> bug in 4.0: comments are deleted when I enter a new move"), and
> then you replied the next day "I found the bug (not comm
2009/11/28 Girolamo Castaldo
> Yes, the problem only occurs with the comment window open in docked mode,
> but if I try to undock it (or any other docked window), it gives me an
> Application Error ("wm manage is not yet supported"), with the following
> details:
>
> wm manage is not yet supporte
2009/11/28 Remco Gerlich
> Pascal,
>
> On Sep 7 I reported the same problem (the subject was "Apparent bug in 4.0:
> comments are deleted when I enter a new move"), and then you replied the
> next day "I found the bug (not commited in CVS yet)".
>
> So possibly the reason you don't see it but we
Remco Gerlich wrote:
> Pascal,
>
> On Sep 7 I reported the same problem (the subject was "Apparent bug in
> 4.0: comments are deleted when I enter a new move"), and then you
> replied the next day "I found the bug (not commited in CVS yet)".
>
> So possibly the reason you don't see it but we do i
Pascal,
On Sep 7 I reported the same problem (the subject was "Apparent bug in 4.0:
comments are deleted when I enter a new move"), and then you replied the
next day "I found the bug (not commited in CVS yet)".
So possibly the reason you don't see it but we do is because you haven't
committed the
; move is also applied to the alternative move.
> This problem is gone - at least, it does no longer reproduce as I
> remember it.
>
Aha (see line 218 of the ChangeLog), this was repaired in version 3.6.10
Possibly with side effects...
> Joost.
>
>
>&
ated, although the appearance is almost opposite: If you enter a
variation after having commented the main move, the comment for the main
move is also applied to the alternative move.
This problem is gone - at least, it does no longer reproduce as I
remember it.
Joost.
>
>
>
>
supported
while executing
"wm manage $f"
(procedure "::docking::undock" line 13)
invoked from within
"::docking::undock .tb1"
(menu invoke)
I suppose OS X 10.6.1 is not fully supported yet.
-[ Received Mail Content ]------
Subject : Re:
2009/11/28 Girolamo Castaldo
> Ok, let's go step by step.
>
> Case 1:
> 1) Create a new game and make a move (eg. 1.e4);
> 2) Add a comment to it and store it;
> 3) Make Black's move (eg. 1...c5);
> 4) Go back to White's move (1.e4): the comment has disappeared.
>
> Case 2:
> 1) Starting from poi
leave the comment window open, you can - in docked mode - even
re-focus the PGN window and see the comment disappear "live".
Joost.
>
>
> -----[ Received Mail Content ]--
>
> Subject : Re: [Scid-users] The comment vanishes
>
> Date : Sat, 28 Nov
o White's first move and
store it;
2) Make a new move for Black (eg. 1...e5) and set it as the new main line (or
replace the previous line);
3) Go back to White's move (1.e4): the comment has disappeared again.
Hope this helps.
-[ Received Mail Content ]------
Subje
2009/11/27 Girolamo Castaldo
> Hello,
>
> I'm using Scid 4.0 on Mac OS X 10.6.1 and I've found an annoying bug:
> if you add a comment to a move, store it and THEN add a move to the
> line or add a new main line, if you come back to the move you added a
> comment to, you'll find it has disappeare
Hello,
I'm using Scid 4.0 on Mac OS X 10.6.1 and I've found an annoying bug:
if you add a comment to a move, store it and THEN add a move to the
line or add a new main line, if you come back to the move you added a
comment to, you'll find it has disappeared. This doesn't happen if you
FIRST add a
29 matches
Mail list logo
