Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354815 - [SysML Block Definition Diagram] Incorrect location stored for Port in notation model
Summary: [SysML Block Definition Diagram] Incorrect location stored for Port in notati...
Status: RESOLVED FIXED
Alias: None
Product: Papyrus
Classification: Modeling
Component: Core (show other bugs)
Version: 0.8.0   Edit
Hardware: PC Windows 7
: P3 major (vote)
Target Milestone: SR1   Edit
Assignee: Yann Tanguy CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-16 07:55 EDT by Yann Tanguy CLA
Modified: 2011-08-19 08:25 EDT (History)
0 users

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-08-16 07:55:14 EDT
Cloned from: 354814: [Composite Structure Diagram] Incorrect location stored for Port in notation model
https://bugs.eclipse.org/bugs/show_bug.cgi?id=354814

See bug#354814 for description.

Concern Port and FlowPort represented by affixed children on Block in this diagram.
Comment 1 Yann Tanguy CLA 2011-08-16 16:35:11 EDT
Fixed in 0.8.1 r5247 & r5248 and trunk r5249.

- PrimaryDrag edit policy added on Block that move Port / FlowPort when resizing
- Fix Port / FlowPort location on the fly on diagram opening
- PostLayoutListener not deactivated after opening diagram, it is necessary for a correct refreshVisuals (parent figure has to be updated for correct side to be calculated).
Comment 2 Yann Tanguy CLA 2011-08-19 05:48:55 EDT
Fix 0.8.1 r5268 / Trunk r5274.
- The fix during diagram opening take into account the case parent element has a default size.

Fix 0.8.1 r5269 / Trunk r5274.
- The show/hide contents does not provide a correct location to Port / FlowPort
	- the fix provided here is definitely not satisfying (simply set Port x to -10)
	- the show hide does not seem to create views correctly and should be corrected
	- the show hide should rely on arrange request rather than trying to guess element locations...