Bug 471769 - Wrong target point location after moving an edge with tree routing style
Summary: Wrong target point location after moving an edge with tree routing style
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 3.0.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-07-03 04:17 EDT by Laurent Redor CLA
Modified: 2015-07-09 09:15 EDT (History)
2 users (show)

See Also:

Attachments
Use case for Sirius 2.0 (3.13 KB, application/zip)
2015-07-03 05:26 EDT, Laurent Redor CLA 		no flags Details
Initial use case for Sirius 2.0 (8.89 KB, application/zip)
2015-07-03 05:36 EDT, Laurent Redor CLA 		no flags Details
Use case (10.09 KB, application/octet-stream)
2015-07-09 09:15 EDT, Belqassim Djafer 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:17:08 EDT 
Steps to reproduce:
1. Import the use case added for bug 467663 Comment 8 (https://bugs.eclipse.org/bugs/attachment.cgi?id=254459)
2. Open the "new DiagramForBug467663" diagram
3. Change the routing style of both edges from "Oblique Style Routing" to "Tree Style Routing"
4. Move the common segment of edges in the middle of EClass1 (between ref1 and ref2) => the target end point is not set on the border of EClass2 but in the middle of the figure.
Comment 1 Laurent Redor CLA 2015-07-03 05:26:21 EDT 
Created attachment 254926 [details]
Use case for Sirius 2.0

The problem seems not exist in Sirius 2.0.x. The use case is not exactly the same, so I'm not sure about this.
Comment 2 Laurent Redor CLA 2015-07-03 05:36:37 EDT 
Created attachment 254928 [details]
Initial use case for Sirius 2.0

Now, it is confirmed. With the same use case, the problem does not exist in Sirius 2.0.
Comment 3 Belqassim Djafer CLA 2015-07-09 09:15:54 EDT 
Created attachment 255086 [details]
Use case

This issue also exists in Sirius 2.0 and 1.0.1.

To reproduce, I have followed the steps of Comment 1 and by using the attached use case.