Bug 471771 - Wrong dropped location for border node with different mapping
Summary: Wrong dropped location for border node with different mapping
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 2.0.5   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard: backport
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-07-03 04:42 EDT by Laurent Redor CLA
Modified: 2015-07-03 09:55 EDT (History)
1 user (show)

See Also:

Attachments
Bug467663.zip: Use case for steps to reproduce (6.80 KB, application/zip)
2015-07-03 04:42 EDT, Laurent Redor CLA 		no flags Details
Bug471771ForSirius2.0.zip: Same use case but for Sirius 2.0 (6.21 KB, application/zip)
2015-07-03 05:43 EDT, Laurent Redor CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Laurent Redor CLA 2015-07-03 04:42:11 EDT 
Created attachment 254920 [details]
Bug467663.zip: Use case for steps to reproduce

The dropped location is not correct for a border node if the mapping is different before the drop and after the drop.

Steps to reproduce:
1. Import the project from Bug467663.zip
2. Open the "new DiagramForBug467663Bis" diagram based on component metamodel
3. DnD border node of c13 to c1 container aside of existing port => KO the dropped port is not located at the correct location.
Comment 1 Laurent Redor CLA 2015-07-03 05:43:36 EDT 
Created attachment 254929 [details]
Bug471771ForSirius2.0.zip: Same use case but for Sirius 2.0

The problem already exists in Sirius 2.0