2009/11/30, Fulvio <[email protected]>: > 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 new variation > 9) The comment is vanished > > It's not a simple bug. > I found that exist a "preMoveCommand" that generate all sort of nasty > behaviors with comments (duplication, erasing, storing changes without > user permission). > 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 indeed difficult to handle, but I think I found the solution. I will test and commit later in CVS. Pascal ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/scid-users
