The contribution is sometimes overlapping with the line/arrow

[Romain Alexandre]

When we drag an impact model element, the weight of a contribution can overlap the line. We should prevent that to happen.

[Cécile Camillieri]

I would also be nice that the line's attach point is better correlated with the location of the reuses to one another. For example in this case the contribution to UnamedGoal2 should arrive on the goal's left side instead of its bottom. And the link from UnamedGoal4 should be start on the top of the container. Generally if a link starts on a side, it should arrive on the opposite side of the linked element. (top -> bottom, left -> right and never top -> left for example)

The best solution to do this would probably be to look at the angle of the line between the center of the two elements.

[Jerry Wei]

References #325: Fixed Cecile's suggestion that the line's attach point shoudl be better correlated relative to position

→ <<cset fdd0e6ba6536>>

[Jerry Wei]

Resolved #325: Fixed issue, contribution value will not overlap contributionView anymore

→ <<cset 143637abe830>>

[Jerry Wei]

References #325: Added variables to clean code

→ <<cset 792f20225a55>>

[Romain Alexandre]

References #325: Send to front children and contribution when dragging an element in the impact model + correct weight position wwhen we pan the background

→ <<cset 81e2787ffde8>>

[Romain Alexandre]

References #325: set the visibility of the whole RelationshipView in the operation shouldUpdate() to true or false if the position is offscreen.

→ <<cset 1fa9c3f3b5b3>>