XML Deserialized graph has corrupted final element?

3 posts, 1 answers
  1. Andrew
    Andrew avatar
    15 posts
    Member since:
    Apr 2013

    Posted 12 Nov 2014 Link to this post

    When diagram.Load( xmlstring) is called, the last element of diagram.Connections has correct Source and Target properties.

    After layout (I believe  diagram.AutoFitAsync but perhaps also diagram.BringIntoView) this last element is corrupted such that the Target property becomes null.

    The corresponding Shape in diagram.Shapes also loses the corresponding IncomingLink.

    So to recap, the Connections/Shapes look correct directly after Load, but then later the last element of Connections loses its Target.

    Because this is the last element of the enumeration I wonder if there is some kind of weird edge case doing this.

    For what its worth I've attached a Visio of the graph. The edge that goes wrong is an inbound edge from "dd" to "Attitudes 6e"
  2. Answer
    Petar Mladenov
    Petar Mladenov avatar
    2882 posts

    Posted 13 Nov 2014 Link to this post

    Hello Andrew,

    We are currently not aware of similar issue reported in the RadDiagram. We tested our OrgChart demo with save / load and re-layout and everything worked as expected. Is it possible for you to elaborate a bit more on your scenario - your ViewModels, your GraphSource, how you save and load ? Is it an option for you to send us an isolated sample in a new support ticket that we can investigate locally and find the root cause of this issue. This will be highly appreciated. Thank you in advance for your cooperation.

    Petar Mladenov

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

  3. DevCraft R3 2016 release webinar banner
  4. Andrew
    Andrew avatar
    15 posts
    Member since:
    Apr 2013

    Posted 16 Nov 2014 in reply to Petar Mladenov Link to this post

    My apologizes -- I created a small simple test project and the bug disappeared. It must be in my own code somewhere. I will let you know if the status changes.
Back to Top