Next Design V2.0 (2.0.1.20104) Release Notes
Table of Contents
- new feature
- Unique Git merge tool for more flexible distributed development
- Partial loading makes light work of even large projects
- UML/SysML Enhanced support for
- Improved ease of migration from existing assets
- UI Customize the UI to further extend Next Design
- Extensibility through extensions
- Improved profile representation
- Numerous new features improve usability
- Applications in general
- V1.1 NOTES ON UPGRADING FROM V1.1 TO V2.0
new feature
Unique Git merge tool for more flexible distributed development
- Distributed development and merging with Git is now supported.
- NOW THAT THE MODEL CAN BE SAVED IN TEXT (JSON) FORMAT, MODEL CHANGE DIFFERENCES CAN BE VIEWED AS TEXT DIFFERENCES.
- Traditional database formats will continue to be available.
- A dedicated conflict detection and merging application (ND Merge) is included to identify and automatically merge conflicts.
- NOW THAT THE MODEL CAN BE SAVED IN TEXT (JSON) FORMAT, MODEL CHANGE DIFFERENCES CAN BE VIEWED AS TEXT DIFFERENCES.
Partial loading makes light work of even large projects
- Partial loading of model files is now supported.
- You can now specify which model files to load or not load, allowing you to load and design model data for your own design scope only.
- If necessary, any model file of the associated destination can be loaded.
- Available only in Enterprise Edition.
- You can now specify which model files to load or not load, allowing you to load and design model data for your own design scope only.
Enhanced UML/SysML support
-
Standardized representation of class diagrams can now be supported.
- Category text can now be displayed above the title of the shape, allowing stereotypes to be represented on the figure.
- Shapes can now be changed individually, allowing the interface to be displayed as icons.
- When multiple labels with the same display position are set for a connector shape, the initial position of the labels is now automatically adjusted so that they do not overlap each other.
- Other related correspondence includes
- Changed to overlay text boxes when editing fields and methods.
- Even if a field name or other information is long, it can be edited without being cut off.
- Changed so that the add button (+ mark) appears on the screen even if the field or method name is long.
- Changed to overlay text boxes when editing fields and methods.
-
Expanded description elements and corresponding functions in sequence diagrams.
- The following can now be described
- Use of interactions
- The use of interactions can be associated with existing interactions.
- notebook
- Supplementary explanations can now be added to sequence diagrams.
- Use of interactions
- Multiple fields can now be specified for message mapping.
- If multiple mappings are specified, all mapped field elements are displayed in the candidate message types.
- Parameters and return values for individual messages can now be edited.
- Now that the model can be replicated, interactions (sequence diagrams) can be replicated.
- The model name of the interaction is now linked to the frame name of the sequence diagram.
- Styles such as background color can now be specified for elements in sequence diagrams.
- The following functions of Next Design are supported in sequence diagrams.
- product line
- Only interactions can be assigned features and products can be enabled or disabled.
- traceability
- Edit and check traces between elements on the Trace Between Editors and Trace page
- Model Difference Display
- Error and search display
- product line
- The following can now be described
Improved ease of migration from existing assets
- Migration from Office Documents
- AN API HAS BEEN ADDED TO RICH TEXT TYPE DATA THAT CAN IMPORT NOT ONLY TEXT DATA BUT ALSO STYLES AND IMAGES.
- When copying and pasting the contents of a Word document into a rich text type field, it is now possible to paste only the text data.
- Improved editability of rich text tables
- Table cells in rich text can now be merged and unmerged.
Customize the UI to further extend Next Design
- EXTENSIONS ALLOW YOU TO ADD YOUR OWN UI. YOU CAN BUILD IN DATA REPRESENTATION AND EDITABILITY SUITABLE FOR YOUR TARGET DOMAIN.
- THE FOLLOWING UIS ARE AVAILABLE FOR EXPANSION
- navigator
- editor
- inspector
- finder
- THE FOLLOWING UIS ARE AVAILABLE FOR EXPANSION
Extensibility through extensions
Multiple profile support for extensions
- Multiple profile names can now be specified in the manifest, allowing extensions to be used in multiple profiles.
- For example, you can import UML/SysML profiles distributed as a package into a profile you have developed, and use the extensions for UML/SysML profiles without modification.
Increased expressiveness through extensions
-
Extension allows changing font styles, such as underlining and italicizing titles depending on the model status.
- EXTENSIONS CAN NOW REALIZE INTERFACE- AND ABSTRACT-LIKE REPRESENTATIONS OF UML CLASS DIAGRAMS ON DIAGRAMS.
-
The extension allows field values from multiple models to be combined and displayed in any format for title, parcel item, and label text.
- View can now be customized with extensions so that fields and methods can be displayed and edited with their types and arguments on the diagram.
- The view can now be customized with extensions to display and edit related end names and multiplicity on the diagram.
-
An extension allows you to specify an alternate string to display if the label is empty.
- An alternate string can now be displayed in the extension to quickly determine which label sets the related end name or multiplicity.
-
Extensions allow you to change or hide individual field and method icons.
-
An extension allows sequence diagrams to be created.
- It is now possible to develop extensions that convert sequence diagram data from other modeling tools and import them as Next Design data.
-
The extension allows you to set the method from which a class is inherited as a message in a sequence diagram.
Customize model editing with extensions
- The extension allows control over whether or not models can be associated.
- Extensions allow you to narrow down the types of models you can add and reference.
- An extension allows for additional initialization processing when adding a model.
- Field values can now be initialized by extensions when adding and duplicating models.
- The extension allows you to add your own display mode to the subeditor's display mode choices. You can arbitrarily specify what the subeditors should display depending on your choice of main editor.
- For example, an extension could add a mode in which, when a model is selected in the main editor, a sub-editor displays the parent of that model.
- At the same time, an extension can now add a display mode so that you can also switch the display target on the "Properties" tab of the inspector.
ADD/MODIFY API
-
Some APIs that were released as a preview version are now officially supported.
- THE FOLLOWING API IS RELEASED AS AN OFFICIAL VERSION.
- Data acquisition and updating of views
- Profile data acquisition
- Operation on distributed development
- THE FOLLOWING API IS RELEASED AS AN OFFICIAL VERSION.
-
THE NEWLY ADDED APIS ARE AS FOLLOWS
-
MODEL-RELATED APIS ADDED
-
IFeature.GetAssignedModels()
: A list of models to which features are assigned can be obtained. -
IFeatureModel.GetFeatureConstraint()
Constraints: Constraints between specified features can be obtained. -
IField.DefaultValue {get; set;}
Initial values of the fields can be manipulated. -
IModel.IsDirty {get; }
You can check to see if the model is in the edited state. -
IProfile.RootPackage
Root package: You can retrieve the root package. -
IField.TypeEnum {get;}
Enumerations of enumerated fields can be obtained. -
INode.NodeStyle
Style Information for Node ShapesINodeShapeStyle
can be obtained. -
INodeShapeStyle.Figure
Shape: Shapes can be acquired and set. -
IModel
to set and retrieve arbitrary string type data in rich text type fields.SetRichTextField(string fieldName, string value)
IModel.SetRichTextField(string fieldName, string value, string format)
IModel.SetRichTextField(string fieldName, string value, string textValue, string format)
GetRichTextField(string fieldName, string format)
IModel.GetRichTextFieldFormats(string fieldName)
IModel.SetRichTextFieldCustomData(string fieldName, string value, string format)
IModel.GetRichTextFieldCustomData(string fieldName, string format)
Notes:
- Existing APIs (ex.
IModel.SetField
method) to set rich text type field values, only the Text format data is updated. Therefore, the set value is not reflected in the display of the rich text type field. - To reflect this in the display of rich text type fields, use the access method for newly added rich text type fields to set the value.
-
-
ADDED API FOR PARTIAL LOADING
IWorkspace.OpenProject()
: Allows you to open a project without loading a split model file.IWorkspace.SetLoadMode()
Model file: You can change the settings when loading a split model file.IWorkspace.GetModelUnitByLoadMode()
: You can retrieve the model unit with the specified loading configuration.IWorkspace.LoadModelUnits()
Model files that have been split into projects can be additionally loaded.- Relatedly, the following allows for manipulation of partially loaded models.
IProject.GetModelByPath(string, string)
by specifying the path of the partially loaded model.IModel
can be obtained.- In a partially loaded model,
IModel.ModelPath
property returns the path from the base element of the unit file. - Partially loaded base point elements are,
MoveTo()
andIModel.Take()
The move operation cannot be performed with the - If there are model files that have not been loaded,
IProject.CreateProductLineModel()
You cannot start a product line with
-
ADDED API FOR SEQUENCE DIAGRAMS
- AN API HAS BEEN ADDED TO ACCESS EACH ELEMENT OF A SEQUENCE DIAGRAM.
ISequenceShape
Sequence Diagram: Common interface for sequence diagram shapes.INoteShape
Note: Note shapes can be accessed.INoteAnchorShape
Note: Access to note anchor shapes that connect the note to the target element.IFragmentShape
Access to composite fragment shapes.IOperandShape
operand figure of a composite fragment.ILifelineShape.Figure
:Property to obtain lifeline shapes.Figure.
added.
- AN API HAS BEEN ADDED TO ALLOW RETRIEVAL OF ELEMENT ATTRIBUTE VALUES.
IExecutionSpecificationShape.Length
Rectangle: The length of the rectangle in the execution specification can be obtained.IMessageShape.SourceY
Y COORDINATE OF THE STARTING POINT OF THE MESSAGE CAN BE OBTAINED.IMessageShape.TargetY
Y-COORDINATE OF THE END POINT OF THE MESSAGE CAN BE OBTAINED.IMessageShape.SelfloopBendsX
X-COORDINATE OF THE BEND POSITION IN THE SELF-CONNECTION MESSAGE CAN BE OBTAINED.ISequenceDiagram.Fragments
Sequence: Allows you to retrieve all composite fragments on a sequence diagram.ISequenceDiagram.Notes
Note: All note shapes on the sequence diagram can be retrieved.ISequenceDiagram.NoteAnchors
Note: You can get all the note anchor shapes on the sequence diagram.ISequenceDiagram.InteractionUses {get;}
: You can get all the interaction use shapes on the sequence diagram.IInteraction.InteractionUses {get;}
You can get all the "Interaction Use".IInteractionUse.RefersTo {get; set;}
Interaction: "Use Interaction" can retrieve or set the interaction associated with it.
- AN API HAS BEEN ADDED TO ACCESS EACH ELEMENT OF A SEQUENCE DIAGRAM.
-
ADDED API FOR DIAGRAM DISPLAY
- Styles can now be applied to any element on a diagram according to its model values.
IViewDefinitions.RegisterGetStyleCallback()
allows you to redefine the process of retrieving a shape's style values in an arbitrary process.IViewDefinitions.RegisterGetTextStyleCallback()
allows you to redefine the process of retrieving text style values in any process.IViewDefinitions.RegisterGetCompartmentItemTextStyleCallback()
allows you to redefine the process of retrieving the style value of a compartment item in any process.
- A formatter/parser can now be applied to any text on a diagram.
IViewDefinitions.RegisterTextValueCallback()
allows you to redefine the text value get/set process with any process.IViewDefinitions.RegisterCompartmentItemTextValueCallback()
allows you to redefine the process of getting/setting the text value of a compartment item in any process.
INodeShapeStyle
A method has been added to allow changing the shape's image.INodeShapeStyle.SetImage(byte[] data, string format = "png")
You can set the image of the shape with the methodINodeShapeStyle.ClearImage()
You can clear the image of a shape with the method
- Styles can now be applied to any element on a diagram according to its model values.
-
ADDED API FOR EDITOR PAGES
IEditorPage.SubEditorModeName
to obtain the display mode name of the subeditor.IEditorPage.SetSubEditorMode(SubEditorMode, string, IModel displayModel)
The custom mode (user-registered mode) can now be selected atIEditorPage.ActiveInspector {get; set;}
: Gets or sets the active inspector in the inspector pane.- THE FOLLOWING API CAN BE USED TO DETERMINE WHETHER A CUSTOM UI EDITOR IS BEING DISPLAYED IN THE MAIN OR SUB EDITOR.
IEditorPage.IsMainEditor
IEditorPage.IsSubEditor
-
ADDED API FOR CUSTOMIZATION OF MODEL EDITING BY EXTENSIONS
- namespace
NextDesign.Core.EditingCapabilities
PROVIDES AN API FOR MODEL EDITING CUSTOMIZATION.CapabilityResults
IEditingCapabilityProviderRegistry
IModelCreationProvider
IModelReferenceProvider
IModelEditorSelectionProvider
ModelCreatableParams
ModelCreatableResult
ModelReferableParams
ModelReferableResult
ModelRelateParams
ModelRelateResult
- namespace
-
ADDED API FOR CUSTOM UI
- namespace
NextDesing.Desktop.CustomUI
TO PROVIDE AN API FOR BUILDING CUSTOM UIS.-
API FOR CUSTOMIZABLE UI.
ICustomUI
ICustomEditorView
ICustomInspector
ICustomNavigator
-
API TO ACCESS FINDER OBJECTS.
IFinder.
IWorkspaceWindow.Finder {get;}
-
OTHER APIS FOR DEFINING CUSTOM UI ATTRIBUTES.
ICustomEditor
ICustomEditorSettings
CustomEditorDefinitionDescriptor
CustomElementDefinitionDescriptor
PropertyDescriptor
PropertyGroupDescriptor
PropertyType
ICustomEditorDefinition
ICustomElementDefinition
ICustomUIRegistry
IViewDefinitions.NewCustomEditorDef()
IViewDefinitions.NewCustomElementDef()
IApplication.CustomUI {get;}
-
- namespace
-
ADDED API FOR WORKSPACE STATUS
IDisplayMode
IWorkspaceState
IWorkspace.State {get;}
BeforeProjectCloseEventArgs
ProjectOpenedEventArgs
-
Event handlers can now be registered for any model attribute change. This interface is in preview release.
IModelEventDispatcher.RegisterPropertyChangedEventHanlder()
: An event handler can be registered to receive property change notifications for a specified model in an arbitrary view model.IModelEventDispatcher.ClearEventHandler()
All registered event handlers can be canceled.
-
We have expanded the interface for accessing Next Design's embedded resources. This interface is available for preview.
IApplication.Resources {get;}
API FOR RESOURCE ACCESS.IResourceUtility.GetIcon()
Icon: You can retrieve the icon resource by specifying the path to the embedded icon.IResourceUtility.GetObjectIcon()
ICON: ICON RESOURCE ASSOCIATED WITH AN API OBJECT CAN BE RETRIEVED.
-
-
THE MODIFIED API IS AS FOLLOWS
-
API CHANGES RELATED TO CUSTOM UI (EXISTING API BELOW, BUT CHANGES WILL BE MADE WHEN DEALING WITH THE ADDED CUSTOM UI)
IEditorPage.ActiveNavigator
Changes the behavior of the property.- "If the custom navigator is subject to
- Custom.${Navigator ID}"
- "For custom navigators,
INavigator
property behavior. If a custom navigator is the target, the following applies:"IsValid
IsEnabled results for: Custom NavigatorIsVisible
Visible results for: Custom Navigator VMItems
Sky CollectionMultiSelection
Determined by custom navigator config valuesName
Custom.${ID of custom navigator}SelectedItems
Sky CollectionTitle
Custom Navigator: Custom Navigator.DispayName
NavigatorSelectionChangedEventParams
Changes the behavior of the class.- No custom navigator selection change event will be issued.
NavigatorOnShowEventParams
/NavigatorOnHideEventParams
Changes the behavior of the class.- "Custom Navigator" The property values of the parameters for the custom navigator shall be as follows
- Name: Custom.${ID of custom navigator}"
-
API CHANGES RELATED TO SEQUENCE DIAGRAMS
ISequenceNodeShape
The inherited source interface of the- Before change: IShape
- After modification: ISequenceShape
ISequenceConnectorShape
The inherited source interface of the- Before change: IShape
- After modification: ISequenceShape
ILifelineShape
The property name has been changed to get the text of the- Before change: Label
- After change: Text
IMessageShape
The property name has been changed to get the text of the- Before change: Label
- After change: Text
IFrameShape
The property name has been changed to get the text of the- Before change: Label
- After change: Text
ISequenceDiagram
The types of properties and methods to retrieve the following shapes defined in theIShap
(orIShapeCollection
) fromISequenceShape
(orISequenceShapeCollection
).ISequenceDiagram.Shapes
ISequenceDiagram.GetShapeById(string)
ISequenceDiagram.GetShapesByModel(IModel)
ISequenceDiagram.GetSelectedShapes()
-
API CHANGES FOR PROJECT OPERATIONS
- Json format projects can now be manipulated.
IWorkspace.OpenProjet()
Json format project files can be opened.IWorkspace.NewProject()
Json: You can create a new project by specifying a profile in Json format.IWorkspace.SaveProjectAs()
Json: You can save project files in Json format.- API TO SAVE THE PROJECT (
IWorkspace.SaveProject()
) with an argument to force overwrite saving even if the model file is not up-to-date.forceOverwrite
added. - IF THE UNIT FILE HAS BEEN UPDATED BY AN EXTERNAL TOOL AFTER THE PROJECT HAS BEEN LOADED BUT HAS NOT BEEN RELOADED, THE FOLLOWING API WITH AN OVERWRITE SAVE
InvalidOperationException
now throws.IProjectUnitManager.SplitModelUnit()
IProjectUnitManager.SplitModelUnits()
IProjectUnitManager.UnifyModelUnit()
IProjectUnitManager.UnifyModelUnits()
IProjectUnitManager.ImportModelUnits()
IProjectUnitManager.AddExternalUnits()
IWorkspace.CleanupProject()
-
API CHANGES RELATED TO PARTIAL LOADING OF MODEL FILES
- Extension event when additional model file loads are performed:
OnAfterModelUnitLoad
is now issued.- Events can be captured by writing them in the extension's manifest file.
- Model file information loaded by additional loading is an event parameter:
ProjectAfterModelUnitLoadEventParams
You can access the site at
IModel.ModelPath {get;}
The reserved word "\partial;" is now added to the base point of the path that can be obtained withIProject.GetModelByPath(string)
argument is "\partial;", the parent model is interpreted as an unloaded model and the model is searched.
- Extension event when additional model file loads are performed:
-
API CHANGES FOR RICH TEXT TYPE FIELDS (NOTE: NO LONGER COMPATIBLE WITH V1.1)
- Rich text type fields.
GetField()
The type of the return value when retrieved withstring
The type was changed so that it is now a type - The value of the grid that corresponds to a field of type rich text.
IGridCell.GetValue()
The type of the return value when retrieved withstring
The type was changed so that it is now a type - The value of the tree grid that corresponds to the rich text type field.
ITreeGridCell.GetValue()
The type of the return value when obtained with type.
- Rich text type fields.
-
CHANGE IN THE TYPES OF MODELS THAT CAN BE RETRIEVED (NOTE: NO LONGER COMPATIBLE WITH V1.1)
- NET Core applications to data types that can be used in .NET Core applications.
NET Core applications are changed to data types that can be used in .NET Core applications. As a result, the minimum and maximum data values will be changed.
INode.Location {get;}
The data type of System.Windows.Point has been changed from System.Windows.Point to System.Drowing.Point. Point to System.Drowing.Point.INode.Size {get;}
Size to System.Drowing.Size Size.INode.SetLocation()
Point to System.Drowing.Point. Point to System.Drowing.INode.SetSize()
Size from System.Windows.Size to System.Drowing.Size. Size to System.Drowing.ISequenceNodeShape.Location {get;}
The data type of System.Windows.Point has been changed from System.Windows.Point to System.Drowing.Point. Point to System.Drowing.Point.ISequenceNodeShape.Size {get;}
The data type of System.Windows.Size has been changed from System.Windows.Size to Size to System.Drowing.
- NET Core applications to data types that can be used in .NET Core applications.
NET Core applications are changed to data types that can be used in .NET Core applications. As a result, the minimum and maximum data values will be changed.
-
Improved profile representation
- Field specification of inherited class
- In the document form grid, fields of inherited classes can now be added as grid columns.
- In the tree grid, fields of a node's inherited class can now be added as child nodes.
- Diagram shapes can now be individually changed to any image or shape, making it easier to identify models of the same type by appearance.
- You can also specify in the profile that the figure cannot be changed.
- The title of an element displayed on a form can now be hidden.
Numerous new features improve usability
-
Model Editing
-
diagram
- The notation of the Delete menu of the diagram context menu has been unified as follows.
- [Remove from Diagram: Removes the currently selected shape from the diagram (changes the previous View Shapes > Hide Selected Shape context menu).
- [Delete Model: Deletes the model along with the currently selected shape.
- When the connector shape is a broken line, changing the bend position solves the problem of the connector shape immediately becoming a straight line.
- THE DEFINITION OF THE SHAPE REPRESENTING THE ER DIAGRAM ITSELF, WHICH IS CREATED WHEN "SHOW ITSELF AS A SHAPE" IS TURNED ON IN THE ER DIAGRAM, IS NOW PROHIBITED FROM BEING CHANGED TO A COMPARTMENT SHAPE WHEN THE SHAPE TYPE IS CHANGED.
- The notation of the Delete menu of the diagram context menu has been unified as follows.
-
sequence diagram
- Changed the model set as the element to be displayed in the inspector when a sequence diagram element is selected.
- Before change: Model specified as the type of the relevant sequence diagram element
- After change: Model of the relevant sequence diagram element
- The order of display of context menu elements in sequence diagrams has been changed.
- Changed the model set as the element to be displayed in the inspector when a sequence diagram element is selected.
-
Form/Tree Grid
- Nodes can now be expanded and compressed in batches from the context menu of the tree grid or form.
- All nodes can now be expanded or compressed at once from the context menu of the document form tree grid.
- From the context menu of the document form tree grid, all nodes below the selected node can now be expanded or compressed.
- In document forms and tree grids, the context menu [Delete from Model] can now delete multiple elements of a model at the same time.
- Revised access keys for the context menu of the Document Form Tree Grid Navigator.
- The ellipsis "..." is now displayed when the text exceeds the width of a cell while displaying a single line in the tree grid. is now displayed when text exceeds the width of a cell in a one-line display in the tree grid.
- The context menu [Delete] of the tree grid column header can now be executed even when the profile cannot be edited.
- Nodes can now be expanded and compressed in batches from the context menu of the tree grid or form.
-
inspector
- The inspector tabs that are displayed for the elements to be displayed in the inspector have been revised.
- The Fields tab is now displayed when selecting compartments in a compartment shape.
- The Metamodel tab is now displayed when selecting compartment elements in a compartment shape.
- When selecting a combo box for an enumerated field on a form, the Fields tab is now displayed.
- The Field tab of the inspector now displays the name of the class in which the field is defined.
- The wording of the description of the elements to be displayed in the inspector at the top of the inspector pane has been revised.
- The order of tabs in the inspector pane has been revised.
- [The order in which the Custom Editor Definition and Custom Element Definition tabs are displayed has been aligned with the order in which the tabs for other view definitions are displayed.
- In the Property Inspector, reference fields could only be displayed up to the first level element, but now they can be displayed arbitrarily further down the reference.
- [Constraints] The inspector no longer retains the elements it displays when you switch pages and return.
- The inspector tabs that are displayed for the elements to be displayed in the inspector have been revised.
-
Error and Search Window
- Type columns can now be displayed in the model from the context menu of the grid's column headers.
- The Type column displays the metamodel icon and metamodel display name for the target model.
- In the error list, the name of the Type column, which represented the error type of an error item, has been changed from "Type" to "Error Type.
- You can now group by any column.
- The keyword filter on the Error tab of the Information Area now applies to all columns.
- The display state of the error window is no longer changed when there are only errors up to warning level at startup.
- Type columns can now be displayed in the model from the context menu of the grid's column headers.
-
product line
- WHEN NO ELEMENTS ARE SELECTED IN THE EDITOR, THE FOLLOWING UI ALLOWS FEATURE ASSIGNMENT OPERATIONS ON THE EDITOR'S OWN MODEL.
- Ribbon [Product Line] > [Model] > [Association], [Delete Association], [Edit Feature Expression]
- Related Feature], [Edit Feature Expression] on the diagram context menu
- In the context menu of the form [Related Feature], [Edit Feature Expression].
- In the context menu of a sequence diagram, [Related Feature], [Edit Feature Expression].
- [The title of the "Edit Feature Conditional Expression" dialog has been changed to "Edit Feature Conditional Expression.
- [The name of the model to be edited is now displayed at the top of the Edit Feature Expression dialog.
- Configuration differences can now be viewed in the product line configuration editor.
- ADDED FEATURE ROWS AND PRODUCT COLUMNS ARE DISPLAYED AS CHANGE DIFFERENCES REGARDLESS OF WHETHER THE CHECK IS ON OR OFF.
- The Configuration Editor does not show the pre-comparison view of the differences, only the current project.
- WHEN NO ELEMENTS ARE SELECTED IN THE EDITOR, THE FOLLOWING UI ALLOWS FEATURE ASSIGNMENT OPERATIONS ON THE EDITOR'S OWN MODEL.
-
be common
- Model Replication
- Model and view display information can now be duplicated together.
- When the multiplicity of a field is 0..1 (single), a single selection finder is now displayed.
- A field with a single multiplicity displays a single-element selection method finder. You can associate a model by selecting the model you wish to associate. You can also unassociate a model by selecting "no model.
- For fields with multiple multiplicity, a checkbox selection type finder is displayed. Models can be associated and disassociated by changing the check status of each model element.
- The display conditions on the [Rich Text] tab of the Ribbon have been changed.
- Before change: Display when a control representing a rich text type field is selected.
- After change: Display when rich text box is in edit state
- Model Replication
-
-
Edit Profile
- You can now duplicate a profile's class diagram. Similar class diagrams can be created based on existing class diagrams.
- Default field names when adding fields have been changed as follows
- Reference related fields: {associated class name}
- Reverse reference related field: "_"+{related source class name}
- Derivation Related Fields: {associated class name}
- Reverse derivation related field: "_"+{related source class name}
- A Metamodel Icon Browse button has been added in the Metamodel Inspector. Clicking on the button brings up the icon selection dialog, allowing you to immediately select a custom icon.
-
Project
- After a project is loaded, the reload confirmation dialog is no longer displayed multiple times when multiple model files are updated outside of the Next Design process.
- If a profile cannot be loaded when opening a project, the project can now avoid being unloaded. Open the project and notify that the profile cannot be loaded.
- When opening a project, we are now notified if a profile could not be loaded.
- You can now open recently used files from the ribbon [File] > [Open] > [Recent Files].
- The maximum number of recently used files displayed has been increased from 10 to 15.
- Recently used files are now synchronized with the taskbar.
- Next Design file icons are now displayed in the sample and template project file icons on the start page.
-
trace page
- The bottom horizontal scroll bar is now always displayed in the tree view of the trace page.
-
ribbon
- The theme has been redesigned to a more modern look.
- THE THEME SET UP UNTIL V1.2 IS NOT MAINTAINED, AND "LIGHT GRAY AND BLUE" IS APPLIED.
- The "light gray x blue-green" and "light gray x orange" themes are not applicable.
- The theme has been redesigned to a more modern look.
-
Performance Improvements
- Improved application startup speed.
- The display speed of the editor, inspector, and trace pages has been improved.
- Improved speed of opening and saving projects.
-
Other
- If sending an e-mail fails, a warning dialog box is now displayed to notify the user of the sending failure.
Applications in general
-
Next Design Main body
-
NET Core 3.1 (.NET Standard 2.0) is now supported.
-
Floating licenses for cloud and on-premise versions are now supported.
-
License authentication at startup now automatically retries if the server connection times out.
-
Support for inter-process communication
- Interprocess communication can now launch Next Design and execute scripts, allowing collaboration between Next Design and other tools.
- For example, Next Design itself can be operated from Office add-ins for Word/Excel.
- Interprocess communication can now launch Next Design and execute scripts, allowing collaboration between Next Design and other tools.
-
Starting with this version, the data version checking mechanism for projects has been changed.
- Project files saved with this version (V2.0) can be opened with Next Design V2.0 or later.
- If you are unable to open a project due to version incompatibility caused by major changes, information will be posted on the support site. Please check it.
-
-
Extension Development
- Different versions of assemblies can now be used for different extensions.
- Native assemblies are now available from extensions.
NOTES ON UPGRADING FROM V1.1 TO V2.0
IN ORDER TO USE A PROJECT CREATED WITH V1.1 WITH V2.0, THE MEASURES DESCRIBED IN THE FOLLOWING NOTES ARE REQUIRED.