This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 149375 - Relationships are drawn crossed
Summary: Relationships are drawn crossed
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram Class (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Trey Spiva
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2008-10-07 14:54 UTC by swedishbricks
Modified: 2008-10-09 01:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description swedishbricks 2008-10-07 14:54:30 UTC
Using the latest nightly build (200810070201), I observed that my class relationship lines are often drawn crossing 
one another. This did not happen with the previous build that I had used ... one from less than a week before.
I was able to easily recreate the problem with a new project:

--> Create a new class diagram
--> Drop three new classes onto the new diagram
--> Create generalization relationships from two of the classes to the one
--> Now move the classes around in the diagram - the relationships remain attached to the generalized class in the 
order of their creation (left to right or top to bottom) instead of relative to their position on the diagram

This behavior does not seem to be dependent upon the type of relationship being represented.

Another way of reproducing this:
--> Place the first class on the drawing
--> Place the second class above and to the right of the first
--> Place the third class below and to the right of the first
--> Draw a relationship from the third class to the first
--> Draw a relationship from the second class to the first
You will find that the relationships are drawn crossing one another. The way to get them uncrossed is to swap 
positions in the diagram with the second and third classes.
Comment 1 Trey Spiva 2008-10-07 17:50:52 UTC
This issue was caused by a fix to the issue 149116.  Now I am using the correct order of the entries when calculating the position.
Comment 2 Trey Spiva 2008-10-07 17:55:54 UTC
Fixed

http://hg.netbeans.org/uml-main/rev/3c96443fa37a
Comment 3 Trey Spiva 2008-10-07 18:25:53 UTC
Reviewed
Comment 4 Peter Lam 2008-10-09 01:21:23 UTC
verified in NB6.5 UML daily build 20081008