Subtile bug in script parsing ?

Hi Dimitris,

This happens on XP, where I have much less of these issues than on Win7.
I'm running scripts in the normal g4c environment i.e. installed g4c, 
not from self-extracting executable.

The following happened ...

I added a "attr font verdana/8" line to a xTextin event somewhere in
the middle of the script and suddenly g4c stopped without any notice
already at the splash window that shows up at launch.
After I removed the line, the script was running again as to be expected.
I added the line again and out of my experience in Win7, I created
a shortcut for the script at the desktop. And yes... the script was
running again as to be expected.

I also tried to load the font at startup and used the font label name
at the xTextin event but that gives the same error.
When I replace the attr font line with a dummy comment line of exactly
 the same length, the script runs again so it has to do with the attr font line.

Because I have the most of these issues on Win7 and it looks like it's
always related to the length of the install path, I have the impression
the problem has only to do with parsing the script when launched.

I run very large scripts with complex things in it like loading gui's in
buffers and decrypt and run them. Using timers and about every other
great feature that g4c offers and I never see it fail. So don't think you
need to look for bugs in that direction. 

I'm aware that my experience and description of it will not immediately
lead to a solution but perhaps we get a bit closer to it?

Chris