This program corrects the following problems/limitations so that you can use the application with more stable quality.

Next Design Main body

Document Form · Rich Text

• We have resolved an issue where, while editing the last row of a form grid, the edit control would sometimes scroll off-screen, making it impossible to view the edited content.
• We have resolved an issue where input became sluggish when the caret moved outside the grid area while continuing to enter text with the vertical scrollbar displayed in the document form grid.
• We have resolved an issue where, in the document form, scrolling upward from a position where rich text was hidden at the top would cause the scroll to stop or revert to its original position once the text came into view.
• We have resolved the issue where images copied from outside NextDesign could not be pasted into rich text.
• We have resolved the issue where search operations in projects with a large amount of rich text took longer in V4 than in V3.

Sequence Diagram

• We have resolved an issue where, even after manually adjusting the lengths of lifelines and execution specifications, those lengths would shrink due to the application's automatic adjustment whenever the project was reopened and edits were made to the sequence diagram.
  • If a user manually adjusts the length to make it longer, it will now retain that length.
  • The length will be automatically adjusted to be shorter only if all of the following conditions are met.
    • The pre-edited version is already the minimum required length (the length immediately after auto-adjustment)
    • Move or delete the last message sent in the same execution specification
    • There are no [composite fragments] or [interaction usage] within the execution specification range (upper and lower bounds) from which the message was sent
  • If the text no longer meets the minimum length requirement due to the addition of messages or other content, it will be automatically adjusted to meet the required length.
    • If execution specifications overlap horizontally on the same timeline, the length of the overlapping execution specification is automatically adjusted so that it is contained within the time interval of the execution specification that starts first.
    • If you make any edits to an existing sequence diagram, the length of the execution specifications displayed side by side on the same diagram will be automatically adjusted. As a result, the overall height of the sequence diagram may increase.
• We have resolved an issue where deleting a message would cause subsequent messages to be moved unintentionally.
• We have resolved an issue where, when a message contained within a composite fragment was deleted, the outer composite fragment would be resized, causing the empty inner fragment to be exposed externally.
  • Applies to: Messages, composite fragments, interaction usage, interaction notes
• You can now move composite fragments that are larger than the viewport in small increments while scrolling.
  • Previously, because the ghost display didn't move in small increments, it wasn't possible to make precise adjustments.
• If the target model for a lifeline or message has not been loaded, the label of the source element will now display "Not Loaded."
• We have resolved an issue where an error occurred when creating sequence diagrams that met specific conditions, such as the first message being an asynchronous message.
• We have resolved an issue that allowed users to set names starting with "___" in the mapping definitions for lifelines.
• We have resolved an issue where changes made to model names in the labels of type-mapped messages in sequence diagrams within the UML/SysML package were not reflected in the actual models.

Change Log

• We have resolved an issue where users were unable to view differences in the editor when comparing the original project with the converted project for projects converted to the profile reference format.

traceability

• We have resolved an issue where the screen would freeze under certain conditions when clicking "Show in Trace View" to display the trace view while the trace page was not visible.
• We have resolved an issue where, when viewing the trace page in matrix format, relationship arrows were not displayed for models containing derived relationships where the source and target were the same entity.
• We have resolved an issue in the Trace Tree View where indirect trace lines were not displayed correctly in certain paths, even though an indirect trace relationship existed.
• We have resolved an issue where indirect traces might not be displayed when applying related filters in the Trace Tree View.
• We have resolved an issue where the Trace Tree View displayed indirect traces even when it contained elements associated with fields that had been disabled via tailoring.
• We have resolved an issue in the Trace Tree View where indirect traces were displayed as enabled even when the trace path contained elements that were disabled in the product.

Manage Extensions

• We have fixed an issue where the scroll bar did not appear in the right-hand pane of the Extensions management dialog, making it difficult to view the contents.

API

• We have resolved an issue where modifying the values of rich text fields via the API caused a discrepancy between the HTML-formatted values used for display and the text values used for searching.
• We have resolved an issue where the error messages for models that had already been split into units differed in meaning between Japanese and English in the IProjectUnitManager.SplitModelUnit method.
• We have resolved an issue where the IViewDefinitions.NewElementDef method could not create a text box definition when the specified field type was Int or Double.

Installer

• We have resolved an issue where the message "Installed successfully" would appear even if the installation of required components failed during the Next Design installation.

Applications in general

• We have deprecated the `Invalid` property, which was stored as internal information in shape definitions but was never used.
  • Projects with invalid properties can still be opened as usual.
  • When saving for the first time in V5, deletion differences for this property may be displayed.

Related Tools

NDMerge

• We have resolved an issue where the setting for "Output compatibility information" was not merged correctly during the merge process.

NDCLI

• We have resolved an issue where an exception occurred when accessing custom editor definitions or custom editor element definitions.

NDExt

• We have resolved an issue where projects were not added correctly to the solution when running the `ndext new` command in an environment with the .NET 10 SDK installed.

Extension Packages

NDGit

• We have resolved an issue in the commit history dialog where it was difficult to set the end date to the same date as the start date.

MarkdownEditor

• We have resolved an issue where, in the Markdown editor, if you entered edit mode after switching models, the values from the model displayed before the switch would appear in the editor, and if you saved your changes in that state, the values would be overwritten with those from the previous model.
• The zoom level of the preview view is now retained even after switching views.