Bug 479036 - Bad feedback and bad edge position when creating an edge with border nodes
Summary: Bad feedback and bad edge position when creating an edge with border nodes
Status: NEW
Alias: None
Product: Sirius
Classification: Modeling
Component: Diagram (show other bugs)
Version: 2.0.5   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2015-10-05 08:24 EDT by Laurent Fasani CLA
Modified: 2015-10-08 03:32 EDT (History)
1 user (show)

See Also:

Attachments
scenario (43.72 KB, video/mp4)
2015-10-05 08:25 EDT, Laurent Fasani CLA 		no flags Details
scenario (112.95 KB, video/mp4)
2015-10-05 08:32 EDT, Laurent Fasani 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 Fasani CLA 2015-10-05 08:24:16 EDT 
Scenario:
Beforehand, create a VSM containing an Edge Creation Tool which applies on an object represented by a node container mapping. That tool should create model elements that are mapped by two border nodes on the container and edge between the two border nodes.
* click on tool and select container node
   => bug1: the source edge feedback is incorrect
* move the mouse on the container
   => bug2: the target edge feedback is incorrect
* select container tool a second time to define the target position
   => bug3: the source and target position of the edge are incorrect

See the attached video
Comment 1 Laurent Fasani CLA 2015-10-05 08:25:39 EDT 
Created attachment 257036 [details]
scenario
Comment 2 Laurent Fasani CLA 2015-10-05 08:32:11 EDT 
Created attachment 257038 [details]
scenario
Comment 3 Maxime Porhel CLA 2015-10-05 10:41:33 EDT 
Implementor will have to describe a validation scenario (and attach a reproduction use case or point to existing data in the test plugins).
Comment 4 Maxime Porhel CLA 2015-10-08 03:32:03 EDT 
It seems that with Sirius 2.0.x on juno 3.8.2 the source element is created on the first clic location and the target element is placed near the top left corner (the snap options have no impact)

while with Sirius 3.1 on Mars.1, the target element is placed regarding the second click and the source element is placed neard the top left corner when the snap is enabled. 
If the snap is disabled, I retrieve the 2.0.x behavior.

The feedback issue is not a regression, the feedback is broken as soos as the source and target edit parts are the same.