Hi,

The template usually contains objects of standard WPF classes and you should check their properties in the MSDN library. The Rectangle from the tutorial's template is a System.Windows.Shapes.Rectangle instance, and the Border element from your template corresponds to System.Windows.Controls.Border.

I hope that helps,
Stoyan

Hi Stoyo,

my TemplatedNode now works fine btw.

I have a question with respect to serialization of the Diagram. I have an XML file format.

There are methods like like Diagram.SaveToXML and Diagram.LoadFromXML that provide serialization to a string that may reside in an XML document.

In my application I'm going to have several CtrlDiagramViews each containing a CtrlDiagram (derived from UserControl) with a Diagram member.

It is hard to acces the Views members (the Diagram) when serializing (and it's ugly code too).

Rather than serializing the Diagram that is of type Control and is member of my class CtrlDiagram I would like to serialize a DataContext object related to the Diagram.

From my point of view a separation between the control (Diagram) and the data behind the control (DataContext) would fit perfectly into WPF thinking.

In the MindFusion reference I cant find such a separation. Or is there any?

Or do you recommend a different architecture for handling several Diagram instances than what I described above?

Regards,
Pontius

I have traced through the test project - the routing problem happens because RecreateLinks returns the links that were removed from the diagram, instead of the newly created ones. Then when you call Router.RouteLinks after the // Error1 comment, it routes the links that are no longer in the diagram, while Diagram.RouteAllLinks will route the new ones.

I can't understand at all why you need to recreate the links each time a node is moved, but if you absolutely need to do that and want to use router.RouteLinks, make your RecreateLink method return the new link, and change this loop:

foreach (DiagramLink link in linkLists[id])
{
	RecreateLink(row, link);
	linksStillExisting.Add(link);
} 

to

foreach (DiagramLink link in linkLists[id])
{
	var newLink = RecreateLink(row, link);
	linksStillExisting.Add(newLink);
} 

I hope that helps,
Stoyan

Hi Stoyo,

thanks for tracking my code.

"I can't understand at all why you need to recreate the links each time a node is moved"

The code I sent to you is a 5% extract of my full code. I just moved the functionality to the diagram_NodeModified(...) method to reduce the complexity of the sample code. So I don't have to write hundert lines of text how to run into the error.
In the full code of course I do not recreate links each time a node is moved. I receate the links after a TableNode has been updated by the user having some new Rows added and some old Rows deleted. Then I 1. save the old links connected to the TableNode, 2. rebuild the TableNode due to the user interaction (i.e. deleting old Rows and creating new Rows) 3. recreate the links for the Rows that are the same as before 4. reroute the links connected to that TableNode.

Your solution is right and it is absolutely my bad. I changed it the way you suggested and it works fine.

On the other hand in the diagram_Loaded(...) code the links are created the first time and they are diagonal without having passed the code above. There is no recreation of obsolete links and the links are diagonal from the very beginning. Do you have any idea why that happens?

More about two way binding later.

Regards,
Pontius

Hi,

It seems you are getting diagonal links in diagram_Loaded because setting DestinationAnchor moves the last point to a new location, after CreateDiagramLink has routed the link. You can call link.Route() after setting the anchor points to get the cascading shape again.

I hope that helps,
Stoyan