Visual UML version 5.0 Update Release Notes

 

Version 5.05 Update (Build #600 – October 25th, 2006)

 

1.       Can now define Operators (Operations with Stereotype = “Operator”) in Classes that target VB.NET. The name of the Operation is the name of the Operator in the generated VB.NET code.
Note: when defining a VB.NET Operator you can use the corresponding Operation’s ‘Property String’ field to define if it is “Widening” or “Narrowing”.

 

2.       When adding an Operator (Operation with Stereotype = “Operator”) to a C# Class, the corresponding Operation’s Visibility is set to Public and its Static option is set to On.

 

3.       When adding an Operator (Operation with Stereotype = “Operator”) to a VB.NET Class, the corresponding Operation’s Visibility is set to Public and its Shared option is set to On.

 

4.       Comments are now properly assigned to the Comment field of corresponding Class Operations when reverse-engineering VB.NET Classes, Methods (Functions & Subs), Properties, Operators, etc.

 

 

Version 5.04a Update (Build #599 – October 20th, 2006)

 

1.       Fixed problem that would result in runtime error #91 when creating and modifying classes after adding new attributes.

 

 

Version 5.04 Update (Build #598 – October 13th, 2006)

 

1.       Fixed problem of incorrect field assignments (Description, etc.) when accessing Model Requirements from Tools menu versus from Model Properties dialog box.

 

2.       Fixed problem with incorrect population/truncation of text of the Description column in grids for Constraints, Responsibilities, Scenarios, Requirements, Test Cases, Tagged Values, Model Glossary Entries, Model Issues and Model Tasks. when the Description field contained Tab characters.

 

3.       Can now add a Self-Association to a Nested Class without causing a runtime error.

 

4.       Fixed a problem that would result in a runtime error #91 after Copying or Moving an Attribute or Operation in a Nested Class.

 

5.       Fixed a problem that would result in a runtime error #91 when trying to generate code from a Class diagram that contained one or more Nested Classes.

 

6.       The Generate Code menu option is no longer enabled for Nested Classes on a Class diagram as code is only generated from the parent/container Class.

 

7.       When generating C++ code, if a Class inherits from a Nested Class, the proper Class name delimiters (“::” rather than “.”) are now used in the name of the other referenced Nested Class.

 

8.       When generating C++ code, if a Class is associated with a Nested Class, the proper Class name delimiters (“::” rather than “.”) are now used in the name of the other referenced Nested Class.

 

9.       When generating C++ code for a Class, the correct Namespace scope (Package Name) is now applied as a prefix to the Methods in the .CPP file that are generated from Operations in Nested Classes.

 

10.   When generating C++ code for a Class, a .H file reference is no longer generated into the .CPP file when a Class Attribute or Association references a Nested Class because the code for the Nested Class is in the same .H file as its parent/container Class.

 

11.   When generating C++ code for Class Attributes or Associations that reference a Nested Class the fully qualified name of the Nested Class is now used. This is the name of the Nested Class prefixed with the name of the parent/container Class using the proper Class name delimiters (“::”).

 

12.   When generating C++ code for Static data members (with a default value) from Class Attributes or Non-Composition Associations a Pointer character (“*”) is now properly applied to the referenced Type in the corresponding definition in the .CPP file.

 

13.   When generating C++ code for Static data members from Composition Associations that reference another Class as the Type, the appropriate definition is also generated into the .CPP file.

 

14.   When generating C++ code for Static data members from Composition Associations that reference another Class as the Type, the Association Role’s Parameters field is now used when creating the corresponding definition into the .CPP file.

 

15.   When generating C++ code for Static data members from Associations that reference another Class as the Type, the name of the referencing Class (the Class that contains the data member) is now prefixed with its Package Name when creating the corresponding definition into the .CPP file.

 

16.   When generating C++ code for Static data members from Associations that reference another Class as the Type, the name of the referenced (by Association) Class is now prefixed with its Package Name when creating the corresponding definition into the .CPP file.

 

17.   When generating C++ code, fixed indentation of inline methods when declared within .H file.<