It's 916 KB when I download it. Could you try again using some download manager or a different browser?

Stoyan

Stoyan,

We saved a blank diagram using the Wpf components, and when we re-open it with DiagramLite, we get a null reference exception when calling the LoadFromXml() method.

Thanks,

Greg

Stoyan,

The de-serialization of custom controls in DiagramLite seems to work okay for the first custom element that you encounter, but does not seem to work correctly for a second element.

Here's the repro:

We have a diagram with two custom controls inside the UIElement tag of two DiagramNodeAdapters. When we open it in DiagramLite, we handle the DeserializeControl as follows:

e.Handled = true;


   var elt = e.XmlElement.Elements().First();


   MyControl ctl = MyControl.LoadFromXml(elt);


   e.Node.Control = ctl; 

We get a valid instance of our control back from our LoadFromXml() method in both cases. But later, when we try to access the second control instance using ControlNode.Control, we get an ArgumentException, saying that the specified argument was out of the range of valid values.

We've even tried inserting two ShapeNodes instead of MyControl in the DeserializeControl handler, and the same thing happens: we get the exception when we try to access the second control.

There are two controls that are loaded successfully, but the following code throws the exception in the "if" statement on the second node:

foreach (ControlNode cn in diag.Nodes)
   {
   try
   {
   if (cn.Control != null && cn.Control is MyControl)
   {
   MyControl ctl =cn.Control as MyControl;
  ctl.RegisterForChildAlarms();
   ctl.SetParent(cn);
   }
   if (cn.Tag != null && cn.Tag is Diagram)
   {
   WireEvents(cn.Tag as Diagram);
   }
   }
   catch
   {
   continue;
   }

   }