Bug 225793 - BorderItemRectilinearRouter conflicts with RectilinearRouter
Summary: BorderItemRectilinearRouter conflicts with RectilinearRouter
Status: RESOLVED FIXED
Alias: None
Product: GMF-Runtime
Classification: Modeling
Component: General (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P3 normal
Target Milestone: 2.1   Edit
Assignee: Alex Boyko CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-04 13:45 EDT by Alex Boyko CLA
Modified: 2010-07-19 12:27 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Boyko CLA 2008-04-04 13:45:27 EDT
Suppose there is a BorderItemRectilinearRouter installed on connections. Suppose we have a connectionbetween two border items that  are located on different shapes and border items are located one exactly above another. There is a rectilinear connection between the 2 border items. The connection is just one vertical segment. It appears that this vertical segment can't be moved in some cases because BorderItemRectilinearRouter might kick in since there are 2 bendpoints only.
Also, the same issue may occur on a 1segment rectilinear connection between 2 non-border item shapes, because of the way the weight is calculated for bendpoints.
Comment 1 Alex Boyko CLA 2008-04-04 14:35:13 EDT
Fix committed to head.

BorderItemRectilinearRouter won't route a connection with 2 bendpoints where the line connecting the points doesn't intersect border item parents. The regular Rectilinear router will route the connection instead.
Weights of bendpoints have been adjusted such that the weight of the first = 0 and weight of the last one = 1. The rest of the bendpoints will have exactly the same weight as before.
Comment 2 Richard Gronback CLA 2008-08-13 13:09:15 EDT
[target cleanup] 2.1 M6 was the original target milestone for this bug
Comment 3 Eclipse Webmaster CLA 2010-07-19 12:27:04 EDT
[GMF Restructure] Bug 319140 : product GMF and component
Runtime Diagram was the original product and component for this bug