I was already for a while plagued with some message that some of my .nxt files showed a bad grammar and were thus not loaded (and off course you can guess, also not executed in the diagrams). I decided to track down what was actually causing all this, and off course it seems like a little thing. At the end of the .nxt file(s) I often had some comments on which ')' I was closing, i.e. something like:
)//ondraw
)// notation
Replacing the two above with
)
)
managed to get the files working again. Probably a small (and off course annoying to find) bug. Hope this helps in improving the code and others who might have the same difficulty getting the nxt files working again
Cheers
Erno
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A few months ago NXT parser was migrated from its original ProGrammar based solution to a more 64 bit friendly .Net based parser. So the input grammars had to be rewritten and some glitches could sneak in. Does your .nxt file work well with StarUML?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I did develop these files back in the old days with StarUML indeed. These comments were considered valid back then, as well as in older versions of the WhiteStarUML, so I do guess it is a result of the new parser version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
and by the way, I consider some of my .nxt files fairly complex, e.g. searching for different associations, crawling through namespaces and adapting the visual appearances based on all of that. Good news is, despite the complex nature, they do work perfectly under the new parser, so in general terms I would say the new parser does it's job very nicely!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nice to know it. The new parser was initially tested with existing nxt files from the ERD module. Fortunately the Scheme based syntax does not have many corner issues.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I cannot reproduce the problem. All comments I inserted are parsed correctly. Maybe you could send a sample test file. Also check if you do not use accidently an older ParserCore.dll hanging somewhere around. The latest version is 1.2.4.0.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It is something unexpected. All recent changes were in Generator and around it. But this is the joy of working with inherited code base. Some innocent code cleaning in one place may backfire elsewhere.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Additionally very big THANKS to you Janusz, because loading project is very quickly now with this version!
Previously, with e.g. 10 DefaultDiagrams, i could see, how every diagram is loaded, and this occupied some time. Now i see all tabs but only selected tab is loaded - fast.
It is good change!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Hi All,
I was already for a while plagued with some message that some of my .nxt files showed a bad grammar and were thus not loaded (and off course you can guess, also not executed in the diagrams). I decided to track down what was actually causing all this, and off course it seems like a little thing. At the end of the .nxt file(s) I often had some comments on which ')' I was closing, i.e. something like:
)// notation
Replacing the two above with
)
managed to get the files working again. Probably a small (and off course annoying to find) bug. Hope this helps in improving the code and others who might have the same difficulty getting the nxt files working again
Cheers
Erno
A few months ago NXT parser was migrated from its original ProGrammar based solution to a more 64 bit friendly .Net based parser. So the input grammars had to be rewritten and some glitches could sneak in. Does your .nxt file work well with StarUML?
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I did develop these files back in the old days with StarUML indeed. These comments were considered valid back then, as well as in older versions of the WhiteStarUML, so I do guess it is a result of the new parser version.
View and moderate all "General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
and by the way, I consider some of my .nxt files fairly complex, e.g. searching for different associations, crawling through namespaces and adapting the visual appearances based on all of that. Good news is, despite the complex nature, they do work perfectly under the new parser, so in general terms I would say the new parser does it's job very nicely!
Nice to know it. The new parser was initially tested with existing nxt files from the ERD module. Fortunately the Scheme based syntax does not have many corner issues.
I cannot reproduce the problem. All comments I inserted are parsed correctly. Maybe you could send a sample test file. Also check if you do not use accidently an older ParserCore.dll hanging somewhere around. The latest version is 1.2.4.0.
Hi
I found problem with NTX.
After instaling 5.6.4.0 I get problems with table.ntx
table.nxt(160): Error exists in For expression.
(I have extended ERD for MSSQL and extended table.ntx)
I found, that problem is with variable i used in for.
If anywhere i has set then for return error.
Simply insert (set i 20) before any for with i.
It is something unexpected. All recent changes were in Generator and around it. But this is the joy of working with inherited code base. Some innocent code cleaning in one place may backfire elsewhere.
Problem fixed in 5.6.5. It looks it had been present since the implementation of the symbol table was changed from list to dictionary in July 2014.
Last edit: Janusz Szpilewski 2015-06-14
I confirm, my nxt works good now.
Additionally very big THANKS to you Janusz, because loading project is very quickly now with this version!
Previously, with e.g. 10 DefaultDiagrams, i could see, how every diagram is loaded, and this occupied some time. Now i see all tabs but only selected tab is loaded - fast.
It is good change!