Changelog for VP Suite 2.1 Build 20060110 (Jan 16 2006)

These changelog for VP Suite demonstrate the enhancements provided in the following products up to and including Build 20060110.

• Visual Paradigm for UML 5.1
• Smart Development Environment 3.1
• DB Visual ARCHITECT 3.0
• DB Visual ARCHITECT SQL 1.0
  

Added support to including Use Case Description information in exporting XMI, and handles Use Case Description information when importing an XMI.

VPProductInfo lProductInfo = ApplicationManager.instance().getProductInfo();
 
String lBuildNumber = lProductInfo.getBuildNumber();
String lName = lProductInfo.getName();
String lShortName = lProductInfo.getShortName();
String lVersion = lProductInfo.getVersion();

A DiagramElement class in VP plug-in defines the visual properties of a model on a particular diagram. VP plug-in now allows you to get the DiagramElements from an IModelElement object.

IModelElement lModelElement = lClassModel;
IDiagramElement[] lDiagramElements = lModelElement.getDiagramElements();

Steps:

1. From Model Tree or Class Repository, select the packages or classes to be moved.
2. Right-click on the selection and select Move... from popup menu. This displays the Move Model dialog box.
   
   
   
3. Select the destination to where the selected classes/packages will be located. If you like you can create a new package to store the selected classes/packages by clicking Create New Package... and providing a package name.
   
   
   
4. Click OK to confirm the changes.
   

Outcome:

After added:

Fixed a bug in which instance specification shape did not refresh itself when closing its Open Specification dialog box to reflect the changes made on its slot value(s).

After bug fixed:

Fixed a critical bug in which a diagram containing a model which has the parent diagram as the model’s child would cause the application to hang.

Fixed a minor bug in which the “set as default for” option in Format Fill Color dialog would show un-meaningful or unreadable model name such as “UseCase” for “Use Case”, “DBTable” for “Entity”.

Fixed a bug in which the background color of a newly created fork node would not follow the default fill color.

Fixed a bug in which ball-and-socket was not drawn when connecting two or more components to the same interface in a component diagram.

Fixed a bug in which open specification dialog box could not be closed when any tagged value definition of the model stereotype was removed before.

Fixed a bug in which an embedded image would not change itself by re-importing even it was modified externally.

In the previous build, when you were unable to provide a valid license key file when starting SDE for Visual Studio .NET or DBVA for Visual Studio .NET for the first time, VS .NET would be locked.

In the previous build, if the column’s name inside a partial table in ERD is different from the corresponding attribute’s name, the generated ORM may cause a runtime error.

Fixed a bug in which Instant Reverse of .NET dll written in C# would not reverse association as connectors.

Fixed a bug in which entering text in a System Response cell in Use Case Description flow of events table by first selecting all content (Ctrl-A) would not overwrite the original text, but appended the entered text to the end of the original text.

After updated:

From now on, for JDBC drivers that are not available for downloading, it will directly shows the failure message rather than showing the proxy setting dialog.

After added: