Community
Participate
Working Groups
An advice should be added to remove Part or Ref. view when the aggregation kind is modified.
Also concerns Value (Property) supposed to be a Composition. The type has to be considered, when set to a new one or when deleted.
Fixed in r4831.
Incorrect refresh when the AggregationKind is set to NONE - Fixed in 0.8.1 (r5354) & trunk (r5355).
Apparently, the pb is only fixed for bi-directional composition links. If one creates a "directed composition" with the BDD palette, then change the aggregation kind of the composite role to "none", the diamond does *not* disappear. To reproduce, create 2 blocks on a BDD, draw one bi-directional composition and one directed composition between the two blocks, then change the two "composite" roles' aggregation to "none" through the property pages. For the bidirectional composition, the diamond disappears, but not for the directed composition. => To be REOPENED?
(In reply to comment #4) > Apparently, the pb is only fixed for bi-directional composition links. > If one creates a "directed composition" with the BDD palette, > then change the aggregation kind of the composite role to "none", > the diamond does *not* disappear. > > To reproduce, create 2 blocks on a BDD, draw one bi-directional composition and > one directed composition between the two blocks, then change the two "composite" > roles' aggregation to "none" through the property pages. > For the bidirectional composition, the diamond disappears, but not for the > directed composition. > Fixed in 0.8.1 (r5397) and trunk (r5398).