if NullOption in tagged values is set to NULL it looks like nullOption have value 'NULL' - in output we get '..... NULL'
BUT
what value is in nullOption? If I add:
(if (= nullOption 'NULL') (set attrName (concat attrName ' This is null')))
then condition is false!
So, have nullOption value 'NULL' or not?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Last time the .nxt file parser went through migration to .Net. I even tested it with ERD but apparently some problems slipped through.
If you are impatient there is WhiteStarUML-5.5.7.1-OldParser.zip in DailiesAndNighties reverting back to the old parser. As I checked the problem with concatenation is not present there.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Look that happened a problem with Variant string hell, when various string types were not recognized as equal. Now it should be fixed and WhiteStarUML-5.5.7.2 is back on track.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
I noticed, that in new releases is problem with extending notations with profiles.
E.g. my lovely ERD...
1.
Now default empty value for ColumName is '(empty)'. This original code (in table.nxt) now not work correctly:
in code above columnName!='' but attrName have concatenated empty string (after '/ ')
so columnName is empty string or not?
if NullOption in tagged values is set to NULL it looks like nullOption have value 'NULL' - in output we get '..... NULL'
BUT
what value is in nullOption? If I add:
then condition is false!
So, have nullOption value 'NULL' or not?
Last time the .nxt file parser went through migration to .Net. I even tested it with ERD but apparently some problems slipped through.
If you are impatient there is WhiteStarUML-5.5.7.1-OldParser.zip in DailiesAndNighties reverting back to the old parser. As I checked the problem with concatenation is not present there.
Look that happened a problem with Variant string hell, when various string types were not recognized as equal. Now it should be fixed and WhiteStarUML-5.5.7.2 is back on track.