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.
reproducible with ent pack 060702 currently such elements as forks are unusable (I think it's quite commen to use forks on activity diagram) Activity edge should be ortogonal to fork by default or it should be possible to reconnect link to any point on fork (at least). steps to reproduce: 1. create activity diagram 2. add partition with two columns 3. add invocation to first column 4. add invocation to second 5. add horizontal forc below invocations and extend the fork to both columns 6. draw activity edges from both invocations to the fork activity edges are connected to fork center, it's better to connect them ortogonally it's impossible to move edges end for better diagram view see activity diagram technical artical for bad usage of forks http://developers.sun.com/prodtech/javatools/jsenterprise/tpr/reference/techart/uml_activity_diagram.html
The edge to the fork works by design, not a defect. I don't see why the curerrent fork is unsuable. Changing the issue type to Enhancement.
Attached is a sample diagram using forks that are very much usable.
Created attachment 32782 [details] Activity diagram
If design is bad it's a defect in design see attachment
Created attachment 32813 [details] all edges are from fork center, looks bad
do you still thin it's a good design?
This is a duplicate of 78324.
low use case not currently impacting our installed user base.
Planned for drawing area upgrade after NB 6.0.
Should not use resolved/later status.
Targeted in the drawing area redesign.
REstoring the original priority and using the NB 6.0 waiver process.
Diagram area bugs waived for 6.0 will also be waived for 6.1.
Still exists in 6.5
I am making this an enhancement request. Since we do not have a good orthogonal router this will not be fixed for 6.5.