AD
Administrator
Syncfusion Team
December 27, 2005 10:46 PM UTC
Hi Chris,
I was able to confirm this as a problem in the Essential Diagram ControlNode class. A fix has been logged and the next update of Essential Diagram will ship with the fix in place. Thank you for bringing this issue to our attention.
You can workaround the issue for now by using a ControlNode''s position in the Symbol.Nodes list or the ControlNode''s child control class information to distinguish it from its sibling.
Prakash Surendra
Syncfusion Inc.,