Changelog for VP Suite 2.1 Build 20060116 (Feb 07 2006)

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

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

Starting from this release (build 20060116), SDE for NetBeans and DBVA for NetBeans will provide support for the 5.0 version of NetBeans IDE.

Extension points of a use case can be reordered through its Open Specification dialog box. Extension points can be shifted up and down. The use case shape will be updated according to the specified order.

After added:

In the previous build, lazy option is provided for instantiating a collection and all of its contained objects when any of the items within the collection is being ‘touched’. Starting from this build, an even smarter option, Extra Lazy, is supported. The Extra Lazy option is provided for instantiating an object only when it is being touched.

After bug fixed:

You can now create content in Report Writer for Frame in sequence diagram. The way to do this is to activate the Model tab, select a Frame from the tree, and then drag a predefined template onto the Report Writer pane.

After added:

In the previous build, when you create a new shape from resource icon, the background color of the newly created shape would follow the default background color set to that type of shape. Starting from this build, the background color would follow the background color of the source shape from where the new shape is created from.

After updated:

The oracle connection URL format for used in .NET ORM is corrected to:

user id=;password=;data source=(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp) (HOST=)(PORT=))(CONNECT_DATA=(SERVICE_NAME=)))

Fixed a bug that caused messages in Sequence Diagram would not be magnified or de-magnified by zooming in and out.

Line weight of message under 100% zoom ratio:


Line weight of message under 200% zoom ratio:

Fixed a bug in which generating HTML or PDF report with “Sequence Diagram Report” template would generate a dead link to the sequence diagram page.

Commit note is the textual description that describes the change made in each commit operation. In the previous build, when a client is disconnected from server after he has input the commit note, the tool will ask for login, and when the client is connect again, the commit note would be lost. This makes the client need to re-enter the commit note. The bug is now fixed, and the note will be memorized before re-logging in.

Users are able to checkout any versions of a teamwork project by opening a version of project from the version tab of the teamwork client dialog box. However, due to the concern of data integrity, old version projects were not allowed to commit to the server again.

In the previous build, when you retrieved the most recent working project from the project listed in the version tab, it also treated that project as an ‘old’ one and would not allow you to commit it to the server. This bug is now fixed such that when the version you opened is the most recent one, the commit ability will not be suspended.

Fixed a bug in which package structure would be demolished when creating a package by dragging a new one over another package which contains a class.

Fixed a bug in which project could not be saved if a sequence diagram was generated from a use case description and the use case description has been deleted before saving.

Fixed a bug in which selecting Call | Operation... from the popup menu of a message would not trigger the operation dialog to be opened when the message type was currently ‘unspecified’

Fixed an exception in which committing changes fro the open specification dialog box of an extension points would throws exception, and block the changes to be saved.

Fixed a performance issue for when saving a project that contains a lot of Note shapes.

In the previous build, when you attempting to delete a Frame in Sequence Diagram, shapes covered by the Frame would be deleted, too, and there is no way to detach those covered shapes from the Frame. Start from this release, deleting a Frame only remove the Frame shape, but not the covered shapes. However, notice that shapes contained by the Frame would still be removed.

Fixed a bug in which moving a class in and out of a package would move the class’s template parameter (if any).

Fixed a problem in which models inside a swimlane would not be treated as children of the swimlane, under the Model Tree.

After bug fixed:

Fixed a bug in which an invalid XMI file would be exported if there exist an relationship which has any side of it pointing to a null reference (no model is pointed)

Fixed a bug in which interface in composite structure allow containing other shapes, which is an incorrect behavior for interface.

Fixed a bug in which the page of EJB Diagram related gesture would not be activated when asking to show the Mouse Gesture help with EJB diagram activated.

Mouse Gesture help - EJB Diagram:

Fixed a bug in which performing undo and redo after created an extension point for a use case may cause the extension point to be missed.

Fixed a bug in which redundant associations would be created when synchronizing a class diagram to and from an ERD with the class diagram having the following class structure: C1 is a super class to C2 and C3, and C2 is associated to C4.

The sample class structure:

Fixed a bug in which activations models would be duplicated when you select them and then send them to a new sequence diagram.

Fixed a bug in which dragging the control point of any stencil object would cause the shape to move, but not resize.
After bug fixed: