It's not uncommon on some of the sites I play to get incorrectly recorded match 
files which when opened in gnu produce a message like:

WARNING: Invalid move: " 16/11 13/11 16/11 13/11" encountered
WARNING: Invalid move: " 11/9 13/7" encountered
WARNING: Invalid move: " 25/20 20/16" encountered
WARNING: Invalid move: " 25/21 8/5" encountered

That is fine. The problem I have though is when I batch analyse say 25 matches, 
go away, and come back hours later expecting it to be done. Unless I've first 
individually opened each one and made sure no such message appears with any of 
them, what sometimes happens is that the whole process stops at the start of 
the second or third match, with an error message awaiting my return. Is it not 
possible for either the buggy match to be analysed anyway or else just be 
skipped rather than wait for some action by me?
_______________________________________________
Bug-gnubg mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnubg

Reply via email to