Community
Participate
Working Groups
When adding/deleting, for instance, a port to a capsule, whereas this capsule is used as capsule part in another diagram -- let's call it diagram A -- diagram A gets automatically changed to reflect the added/deleted port of the capsule part. Since bug 507059, we are handling such changes gracefully and hide them, since they are automatically applied and are just a consequence of adding/deleting a port to a capsule. However, if now diagram A is deleted through a capsule deletion, those indirect automatic diagram changes in diagram A are reported as conflict with the deletion of diagram A, even though those automatic diagram changes are merely just a result of an unconflicting change (the deletion/addition of a port to another capsule). Thus, we require special conflict handling for those automatic diagram changes.
(In reply to Philip Langer from comment #0) > When adding/deleting, for instance, a port to a capsule, whereas this > capsule is used as capsule part in another diagram -- let's call it diagram > A -- diagram A gets automatically changed to reflect the added/deleted port > of the capsule part. Since bug 507059, we are handling such changes > gracefully and hide them, since they are automatically applied and are just > a consequence of adding/deleting a port to a capsule. > > However, if now diagram A is deleted through a capsule deletion, those > indirect automatic diagram changes in diagram A are reported as conflict > with the deletion of diagram A, even though those automatic diagram changes > are merely just a result of an unconflicting change (the deletion/addition > of a port to another capsule). > > Thus, we require special conflict handling for those automatic diagram > changes. This will need a mention in the release notes for 1.0
