Constraints

• If the project's file structure has been changed, the difference list window (conflict analysis window) cannot be displayed.

• If the deletion of a design model is undone when resolving a conflict, the model order may not revert to the order before deletion.

• Example of editing that causes a conflict

• Own: Delete the design model.

• Other: Edit the model that will be deleted by Own.

• Even if a conflict occurs when changing the tagged values ​​of a design model, the direction of application cannot be specified. In this case, your own changes will always be applied.

• Example of changes

• Own: Edit the tagged values ​​of the design model.

• Other: Edit the same tagged values ​​as Own.

• If you change the hierarchy of a model file in Own, merge it in Other, and split another model using the same model file name, the conflicting files will not be considered strong conflicts, potentially resulting in an inconsistent model as a merge result.

• Model files that are referenced are not compared, and differences cannot be seen on the comparison results screen.

• In difference comparisons including submodules, the commit information of the comparison target is displayed as additional information in all editors.

• In NDGit difference comparisons including submodules, if the profile of the open project is not included in the repository being compared, the model differences may not be displayed.

• If a metaclass is deleted, the corresponding model will not be loaded in the comparison target project, and therefore the differences will not be displayed.

• If a field is deleted, the corresponding model will not be loaded in the comparison target project, and therefore the differences will not be displayed.

• If an enumeration value is deleted, the corresponding model will not be loaded in the comparison target project, and therefore the differences will not be displayed.