Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348324 - [SysML Block Definition Diagram] Part and Ref. graphical refresh when aggregation changes
Summary: [SysML Block Definition Diagram] Part and Ref. graphical refresh when aggrega...
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.8.0   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Yann Tanguy CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-05 09:15 EDT by Yann Tanguy CLA
Modified: 2011-09-07 11:22 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yann Tanguy CLA 2011-06-05 09:15:23 EDT
An advice should be added to remove Part or Ref. view when the aggregation kind is modified.
Comment 1 Yann Tanguy CLA 2011-06-06 08:13:02 EDT
Also concerns Value (Property) supposed to be a Composition.

The type has to be considered, when set to a new one or when deleted.
Comment 2 Yann Tanguy CLA 2011-06-06 08:22:40 EDT
Fixed in r4831.
Comment 3 Yann Tanguy CLA 2011-09-02 03:56:39 EDT
Incorrect refresh when the AggregationKind is set to NONE - Fixed in 0.8.1 (r5354) & trunk (r5355).
Comment 4 Alain Le Guennec CLA 2011-09-07 04:42:40 EDT
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?
Comment 5 Yann Tanguy CLA 2011-09-07 11:22:23 EDT
(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).