| CascadingDifferencesFilter and changes in moved objects [message #1369880] |
Tue, 20 May 2014 19:43  |
 Andreas Mayer
Messages: 11
Registered: April 2014 |
Junior Member |
|
|
Hello,
if a new element X was added to a model and X has descendants of its own, then the default engine creates ADDs for X and each of its descendants in the comparison result. The structure merge viewer in turn provides a filter (CascadingDifferencesFilter), which is enabled by default and will hide all of these ADDs except the one for X. This seems to be a reasonable decision, because the descendants are added to the model as part of X.
However, this filter also applies to ADDs in objects that have been moved. For example, if an EAttribute x has been moved from EClass A to EClass B and an EAnnotation has been added to x, then you will only see that x was moved, but not the addition of the EAnnotation -- until you disable the filter for cascading differences. In my opinion, changes in moved objects should not be treated as cascading differences and therefore not hidden by default, because they are unrelated to the move.
Andreas
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.01853 seconds
] 
Search
Help
Register
Login
Home
