Skip to main content

NDMerge V1.1 release note

V1.1.2.30206

  • Solved the problem that a project in DB format that contains editor records without layout information could not be merged.
  • Resolved an issue where profile changes may not be merged correctly.
    • Changes such as moving the existing element to the child element position of the newly added element
    • Changes that remove the original parent element after reparenting an existing element
  • Solved the problem that a project with no trace setting information in the base could not be merged correctly even if it was merged after adding the trace setting information.
  • Changed to log notification that information on Own side was adopted by merging when design models with the same Id were added on Own side and Other side.
  • Changed the character code of the output string to the console to UTF-8 (without BOM).
  • Solved the problem that a conflicting merge was treated as successful when a merge conflict and a schema version update occurred at the same time.
  • Solved the problem that the merged project could not be opened when project files with split profiles were merged.
  • Solved the problem that changes to "Title display direction" in form control definitions may not be merged correctly.