Hi Stoyan,

Thanks
I confirm that the crash has been fixed! It was quick!

-1- I got another crash while routing a single node (I'm not sure if I'm allowed to use NewRouter.RouteLink() however 8)).

Additional information: non-adjacent tiles in Tile.Merge!

   at MindFusion.Diagramming.Tile.Merge(Tile tile1, Tile tile2)
   at MindFusion.Diagramming.RoutingTree.x260baf72fdd85c7c()
   at MindFusion.Diagramming.RoutingTree.CreateRoutingTree(Diagram diagram)
   at MindFusion.Diagramming.NewRouter.RouteLink(DiagramLink link) 

-2- Also, it's minor since I found only 1 occurrence in all my graphs, but I have one unecessary turn. I'll send the saved XML & screenshot for you.

-3- Once again something minor, but sometimes the path taken is weird. If it is easy to fix, it would make more sense that a link goes toward its destination where there is the appropriate place instead of going around an obstacle for no obvious reason. I'll send screenshots for that as well (it's the same XML).

-4- I noticed that manually routing some links can be quite long. I do it when a container gets moved, resized or unfolded (there might be other cases, I'm not sure). By example, the following code executed on a container that has about 50 nodes in it takes much longer than calling NewRouter.RouteAllLinks (on a diagram that has over 400 links):

public void RouteRelatedLinks(DiagramNode node)
{
    foreach (DiagramLink link in this.diagram.Links)
    {
        if (link.Origin == node || link.Destination == node || link.Intersects(node))
        {
            NewRouter.RouteLink(link);
            this.Invalidate();
        }
    }

    if (node is ContainerNode)
    {
        ContainerNode comment = (ContainerNode)node;
        if (comment != null && comment.SubordinateGroup != null && comment.SubordinateGroup.AttachedNodes != null)
        {
            foreach (DiagramNode childNode in comment.SubordinateGroup.AttachedNodes)
                RouteRelatedLinks(childNode);
        }
    }
} 

Could I use RoutingTree somehow? It seems to be used in RouteAllLinks...

Thanks a lot!
Marie

Hi Stoyan,

No, I did not get the crash in the same graph (it might be there as well, I don't know).

I'll send you the file. However, it's not a 100% repro. Just move the left-most node and eventually it'll crash (I call RouteRelatedLinks everytime a node is moved).

I got another crash while doing the same thing (It was a null exception):

   at MindFusion.Diagramming.RoutingTree.Eval(Tile previous, Tile current, Tile next)
   at MindFusion.Diagramming.RoutingTree.Route(Tile start, Tile end)
   at MindFusion.Diagramming.NewRouter.x1a552bcef2b91b0f(DiagramLink xe9c763083b68a7ee, RoutingTree x28fd8f9c33fc7c8e, List`1 xa1b0e28271fd2a7c)
   at MindFusion.Diagramming.NewRouter.RouteLink(DiagramLink link, RoutingTree routingTree)
   at MindFusion.Diagramming.NewRouter.RouteLink(DiagramLink link) 

Thanks!
Marie

Hi Stoyan,

1, 2, 3 & 4) All good! The crash is gone and I'm looking forward to 5.3! Do you know when that release is planned?

Thanks for you great help!
Marie

Hi Stoyan,

I'll test your beta version early next week.

Thanks for your help
Marie

Hi Stoyan,

I'm really sorry if it took so long for me to test it, but I have been really busy we my own release...

Now I am dedicated again to our Flowchart component .

I tested the new version and the links all seem to take the same vertical path when the graph is big enough... The user can't follow the path visually since the links overlap (even if they do not go towards the same point).

Could this be fixed?

Thanks as always!
Marie

p.s. I'll send you the screenshot & XML by email...

Hi Stoyan,

I have been suggested to turn off routing to see if it would yield better results.

I am trying to have bezier links.

I set:
diagram.LinkStyle = Bezier
diagram.RouteLinks = false

I get mostly straight links (plus 1 or 2 bezier links and 1 or 2 weird curves). I was wondering if there is something else I need to do to get bezier links?

Thanks,
Marie

p.s. I'm using the beta 5.3 version.

Hi,

This happens because selection handles of the active item take precedence when hit-testing, and by default the whole interior of a container is considered its move handle. You could change the container's HandlesStyle to a value that start move operations only from the selection frame. Another workaround is to set ModificationStart = AutoHandles.

I hope that helps,
Stoyan

Hi Marie,

Setting diagram.LinkStyle = Bezier will affect only new links, and won't change existing links, or ones that are loaded from a file.

At this time you could achieve -2- using a custom BehaviorBase derived class. We'll change the hit-testing of the standard class for the next release.

Stoyan