I think this patch fixes it... but perhaps there are other areas where
it can be over-run ?
BTW, All nags after 200 were off by 1 because of a duplication in the header.
S.
On Mon, Jul 1, 2013 at 8:21 AM, Steve A wrote:
> Oh ok. 224 is the last *standard* NAG, but there is no bounds checking.
>
Oh ok. 224 is the last *standard* NAG, but there is no bounds checking.
S.
--
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_
Yes, something bad is happening. Try for example storing NAG 239 in
the comment editor nag entry box.
String PSKKQDRTBLNR is shown, which is an unrelated internal string
from here: game.cpp
const char * langPieces[] = { "",
"PPKRQDRTBFNC", "PPKRQDRTBANC", "PBKKQDRTBLNS",
"PPKRQDRTBANC", "Pp
$501 is not a valid NAG,
http://en.wikipedia.org/wiki/Numeric_Annotation_Glyphs
Not sure why SCID does not audit the NAG. If you replace $501 with $50
(e.g), it seems to work ok.
On Sun, Jun 30, 2013 at 8:58 AM, Kevin Taylor wrote:
> Hi,
>
> When I import the following PGN file SCID crashes.
Hi,
When I import the following PGN file SCID crashes. Could any tell me
if this is an invalid PGN? If it is a valid PGN file, it would be
better if SCID handled the import error gracefully. ;-)
Here is the contents of the file. I've also attached it.
[Event "#5"]
[Result "*"]
[SetUp "1"]
[FEN "
