Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic Routing and Layout with 5.3.1 (Read 1188 times)
cbh
YaBB Newbies
*
Offline


I love YaBB 1G - SP1!

Posts: 2
Joined: Sep 3rd, 2009
Routing and Layout with 5.3.1
Sep 3rd, 2009 at 9:53am
Print Post  
Hi,
I have upgraded from version 4.x to 5.3.1 and I noticed many changes in routing and layout classes and options.
I 'm using Bezier style for links and TreeLayout.
After Upgrade behavior is quite different for routing and Layout.
I' ve changed Diagram's LinkRouter to a GridRouter and routing is closer to 4.x routing.

I 've red documentation and some information are missing:
When RoutingOptions are involved ? (QuickRouter, LinkRouting, AutoRoute, used with Layout ?)
What means values for cost members, what is impact if I increase or decrease value ?

In fact I was using TreeLayout then a custom algorythm to have same result as new FlowChartLayout but with Rounded link, will rounded links be supported for FlowChartLayout in upcoming version ?

I have also noticed 2 bugs:
In Diagram Properties, when you set LinkRouter to "(none)" (Diagram.LinkRouter = null in InitializeComponent) a crash occurs when adding first shape into diagram.

With a diagram with handred of shapes, PathFinder.FindLongestPath can loop and memory can't stop increasing.

Thanks for Help.
CBH.
  
Back to top
 
IP Logged
 
Stoyo
God Member
*****
Offline


MindFusion support

Posts: 13230
Joined: Jul 20th, 2005
Re: Routing and Layout with 5.3.1
Reply #1 - Sep 3rd, 2009 at 10:29am
Print Post  
Hi,

Quote:
When RoutingOptions are involved ? (QuickRouter, LinkRouting, AutoRoute, used with Layout ?)


The costs in RoutingOptions are used only by GridRouter, so auto-routed links are affected by RoutingOptions values when diagram.LinkRouter is set to a GridRouter instance. In fact we plan to merge most of RoutingOptions into GridRouter, and move the remaining properties into Diagram (e.g. TriggerRerouting).

Quote:
What means values for cost members, what is impact if I increase or decrease value ?


GridRouter evaluates many paths by summing the costs associated with every bend, crossing or length unit in the path (TurnCost/CrossingCost/LengthCost). From the found paths, it chooses the one with lowest total cost.

Quote:
In fact I was using TreeLayout then a custom algorythm to have same result as new FlowChartLayout but with Rounded link, will rounded links be supported for FlowChartLayout in upcoming version ?


I guess we'll get to this at some point, but can't guarantee when we'll implement it. At this time you could enable diagram.RoundedLinks to get a similar effect, even with polyline and cascading links.

I hope that helps,
Stoyan
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint