Visual UML version 3.26 Update Release Notes
Version 3.26 Release (Build #484 –
1. Fixed a problem changing the number of swimlanes on an Activity diagram.
2. Fixed a problem that could result in an error after choosing the “Select
In Model Explorer” menu option when right clicking on an Interface of a Class
or Component on a diagram and then attempting to drag-and-drop that Interface
from the Model Explorer onto the diagram.
3. Extended the life of the trial product version.
4. Fixed a problem that would result in a parser error when attempting to
reverse-engineer a VB.NET code file that contained a Class that in turn
contained a procedure (Sub or Function) that included the MustOverride keyword.
Or, the declaration of a subsequent Sub or Function would be absorbed into the
Code property of the Operation created from the procedure with the MustOverride
keyword. (also in v3.25b)
5. Fixed some problems saving and opening model files saved in XML file
format, in particular problems with adding Lifelines and Activations to Objects
on Sequence diagrams. (also in v3.25a)
6. Fixed a problem that would result in a run-time error # 13 when trying to
import a model from Rational Rose using the trial
version of Visual UML 3.25. (also in
v3.25a)
Version 3.25 Release (Build #482 –
1. Fixed a problem that could cause Visual UML to fail with a run-time error
# 91 when attempting to select Interfaces attached to Classes on Class
diagrams, or Components on Component and Deployment diagrams, after copying a
Package that contained a Class diagram that contained a Class with one or more
Interfaces. Or that contained a Component or Deployment diagram that contained
a Component with one or more Interfaces.
2. Fixed a problem that could cause Visual UML to fail with a run-time error
# 91 when attempting to re-open a Model in which a Package was copied that
contained a Class diagram that contained a Class with one or more Interfaces.
Or, that contained a Component or Deployment diagram that contained a Component
with one or more Interfaces.
3. Fixed a problem that could cause Visual UML to fail with a run-time error
# 91 when attempting to edit the properties of an Association between a pair of
Objects on an Object or Collaboration diagram that were not derived from a Class
or Actor.
4. Fixed a problem that could cause Visual UML to fail with a run-time error
# 91 and/or redraw diagrams after renaming an Interface Class in a model that
had the Interface added to a Class or Component in a certain way on the
Interfaces tab in the Class or Component Properties Editor dialog box.
5. Fixed a problem that could result in an inability to save a Model under
certain circumstances when a reference to a Class assigned to a Component could
not be resolved.
6. Fixed a problem that could result in an inability to save the Model after
reverse-engineering a VB project that contained references to class, module,
etc. files that no longer exist and creating a Component for the VB project in
which the Component referenced the non-existent Classes.
7. Fixed a problem whereby Realizations would be converted to
Generalizations when creating a Class diagram during reverse-engineering of C#,
Java, VB.NET code.
8. Fixed a problem that could result in an error #457 when
reverse-engineering a C# Class again
into the Model, and that Class already exists in the Model, and the Class being
reverse-engineered contained more than one variable with the same name that
differed only in case (for example: myvariable and MyVariable).
Version 3.24 Release (Build #479 –
1. Fixed a problem that could cause loss of diagram scrolling ability using
the scrollbar, keyboard, or mouse wheel after editing a diagram involving
clicking the right mouse button on a connection (association, dependency,
generalization, message, transition, etc.) or interface.
2. Fixed a problem that could result in a "Run time error '91'" error message when
trying to save a Profile.
3. Updated the XML (Schema) Modeling
profile to include the XSDall stereotype.
4. Fixed incorrect XSD (XML Schema) data
type by changing “data” entry to “date” in XSD language configuration file:
XSDDataTypes.Ini.
5. Fixed some minor problems
reverse-engineering C# code.
6. A Role Name is no longer applied to
an Association that did not already have a Role Name when generating Class code
into the Class code window.
7. Fixed a problem whereby the Name of a diagram being displayed in the
caption of a diagram window would appear incorrectly when performing a function
(such as rename) on an object on the current diagram that resulted in
propagation through other open diagrams.
8. Fixed some problems with the
formatting of XMI files when the ‘Format XMI File for Readable XML’ option in
the Export Options dialog box was set to on (checked).
9. Includes the bug fixes, etc. that
were previously released in the Visual UML version 3.23a update (see below).
Version 3.23a Release (Build #478
–
1. Fixed a problem that could result in a "Run time error '76', Path not found" error
message when generating a database schema from a Package, Class diagram,
Component, individual Class, etc. This would typically occur if the directory
that the database schema was generated to was renamed, moved or deleted. This
error would also be received when clicking on a Class in the Model Explorer or on
a Class diagram while the Class Code window was enabled due to the dynamic code
generation into the Class Code window that occurs when selecting a Class.
2. The Model Explorer and Class Code
window are now disabled during the importing of a Rose model. This
significantly improves performance.
3. The Rational Rose Importer now
accommodates un-named objects such as for Classes, Nested Classes, Parameters,
etc. without generating errors or requesting object names.
4. The options (on the Object/Interaction Diagrams tab in the main Options
dialog box) for suppressing the display of the Object Name or Class Name for
new Objects are no longer ignored if an Object is added to an Object,
Collaboration, Sequence, etc. diagram by dragging and dropping an Actor or
Class from the Model Explorer.
5. Fixed a problem that could result in Deployment diagrams in pre-version
3.0 Model files being upgraded incorrectly to version 3.0 or later format, with
the result that they could generate a "Run-Time Error 13” error when opened in Visual UML
version 3.x even after saving and re-opening in version 3.x.
6. Fixed a problem that would result in
a parse error when reverse-engineering Java classes with fields that had no
type.
Version 3.23 Release (Build #477 –
1. The name of the diagram displayed in the Tab (in tabbed MDI mode) or
Caption (in standard MDI mode) of a diagram window is updated when a diagram is
renamed.
2. Fixed a problem that could result in a “box # or line # does not exist –
unable to draw diagram” error after deleting an object lifeline or activation
from a sequence diagram while the diagram navigation window was enabled.
3. Fixed a problem that could result in the loss of Tagged Values that were
added using the Add and Insert buttons in the Tagged Values Editor dialog box.
Similarly for Class Constraints and Class Responsibilities.
4.
The
‘Where Used’ option is now available for Operations in Classes in the Model
Explorer so you can get a list of the Interaction (Sequence and Collaboration)
diagrams that the Operation is used on as a Message.
5.
Fixed a problem that could
result in a run-time error when renaming certain objects (such as Classes and
Components) that were connected/related to certain other object types (such as
N-Ary Associations and Objects).
6. When generating Attributes for VB.NET Classes, Properties, Procedures,
etc. from Tagged Values in Visual UML, empty parentheses are now appended to
the Attribute Name (derived from the Tag Name enclosed in “<>”) if there
is no value specified (in the Tag Value field) and the Attribute Name does not
have “()” appended to it. For example, an Attribute of “MyAttribute()” is
generated from a Tagged Value with Tag Name = “MyAttribute” and no Tag Value.
If an existing Tagged Value has a Name with “()” appended the “()” is ignored
and removed.
7. When reverse-engineering Attributes for VB.NET Classes, Properties,
Procedures, etc. to create Tagged Values in Visual UML, empty parentheses are
no longer appended to the Tag Name (derived from the Attribute Name enclosed in
“<>”) if the Attribute has no value (I.e. Attribute has empty
parentheses). For example, an Attribute of “MyAttribute()” results in a Tagged
Value with Tag Name = “MyAttribute” and no Tag Value (was previously created as
Tag Name = “MyAttribute()”).
8. Fixed a problem whereby reverse-engineering VB.NET code files would fail
if the following format was used for defining inheritance: Class MyChildClass :
Inherits MyParentClass (I.e. use of a colon character preceding the Inherits
statement which is not on a new line).
9. Fixed a problem that could result in the creation of an un-named Package
when reverse-engineering C#, Java or VB.NET class files in which classes
inherited from and/or implemented multiple other classes/interfaces in an
unspecified (i.e. the same) namespace and the inheriting/implementing class was
in a namespace whose name contained a period character (.). In this case, the
classes/or interfaces being inherited/implemented would be placed in an
un-named Package rather than in the same namespace as the inheriting/implementing
class.
10. Fixed a problem that could result in failure to parse a C# code file
containing a class that inherited from a type shortcut such as “object” rather
than “Object” or “System.Object”.
11. When generating Visual Basic for Inheritance, fixed some problems
generating “stub” code in the Child Class for Functions, Subs, etc. defined by
Class Operations in the Parent (Base) Class in Generalizations for which the
‘VB Inheritance Type’ (on the VB tab in the Generalization Properties Editor
dialog box) has been set to “Implementation (Faked)”. The “stub” code is now
generated in the Child Class even for Operations in the Parent (Base) Class
that have a stereotype of “Method”, etc.
12. Fixed a problem that could result in a “Package {…} does not exist!”
error after deleting a Package that contained an open diagram from a
sub-Package.
13. Assorted usability updates to the Tagged Values Editor dialog box. Plus,
the Class Constraints Editor dialog box and the Class Responsibilities Editor
dialog box.
Version 3.22 Release (Build #476 –
1. Fixed a problem that could cause a run-time error when removing an
Interface from a Class on a Class diagram. (also
fixed in v3.21a)
2. Fixed a problem that could result in a run-time error #6 when generating
code from Classes containing Operations with very large (>32K characters)
method code bodies. This would also result in the same error when clicking on
the Class in the Model Explorer or on a Class diagram while the Class Code
Window is enabled. (also fixed in v3.21a)
3. Inline methods for C++ are now properly generated into the .H file (rather
than incorrectly into the .CPP file as was previously the case) if the corresponding
Operation’s ‘Inline’ option is set to on (checked). Also some fixed problems
with the ordering of Inline methods for nested classes for C++.
4. Fixed some problems with the ordering of C++ method declarations in the
.CPP file, especially for nested classes.
5. Fixed several problems with the insertion of supplementary “Visual UML”
comments and indents and blank lines in the generated code when generating code
to C++, C#, Java and VB.NET with the ‘Do Not Include Comments Generated By
Visual UML’ option in the Code Generation Options dialog box set to off
(unchecked).
6. Changed the style of the command buttons and the class name field at the
top of the Class Code Window.
7. Can now change the font used for the contents of the Class Close Window
by clicking the new Code Window button on the Colors/Fonts tab in the main
Options dialog box.
8. Added a ‘Deep Delete’ option to the pop-up editing menu for objects on
diagrams. This option differs from the ‘Delete’ option in that it deletes the
object from the Model rather than just from the current diagram. When the
object is deleted from the Model in this way, the object deletion is propagated
through all diagrams, etc. that used that Model object, just as if it were
deleted via the Model Explorer. This option is enabled for object types on
diagrams that are rooted in the Model (i.e. Actors, Classes, Components, Nodes,
Packages, Use Cases, Associations, Dependencies, Generalizations and
Realizations).
9. Can now add Tagged Values to the Start and End Roles of Associations. This
was achieved by adding Tagged Values buttons to the Start and End groups on the
Roles tab in the Association Properties Editor dialog box.
10. Can now add Descriptions to the Start and End Roles of Associations. This
was achieved by adding Description buttons to the Start and End groups on the
Roles tab in the Association Properties Editor dialog box.
11. Added ‘New’ (for C#, VB.NET, VB6, etc. properties) and ‘WithEvents’ (for
VB6 properties) options to the Attributes tab in the Start and End groups on
the Roles tab in the Association Properties Editor dialog box. These new
properties of Association Roles are used as appropriate in code generation for
applicable languages.
12. When generating VB6 code for Classes with Associations, the (new) ‘New”
and ‘WithEvents’ options of Association Roles are taken into account and the
resulting code is the same as for generating properties from Class Attributes
using the ‘As New’ and/or ‘WithEvents’ options. The ‘As New’ and ‘WithEvents’
statements are also taken into account and applied to Association Roles when
reverse-engineering VB6 Classes and deriving Associations from them.
13. When generating VB6 code for a Class with an Aggregation or Composition
Association, a “New” modifier is no longer applied to the target type, unless
the Association Role’s ‘New’ option is used.
14. Added Help buttons to the dialog boxes for reverse-engineering databases.
15. Added a ‘Display On Top’ option to the Grid tab of the main Options
dialog box that enables the drawing grid to be drawn on top of the objects on
diagrams.