ControlNode Name property overriden

[Mark Eborn]

Hello,

I recently upgraded to Essential Studio version 17.2.0.34 (using the .NET 4.0 assemblies), and I'm experiencing a new issue. Basically, when a ControlNode is appended to the diagram model, it gets renamed "1", "2", etc, overriding the name it was given.  See the basic code snippet below:

    var node = new ControlNode(myControl, new RectangleF(0, 0, 100, 100))
    {
        Name = "test"
    };

    // node.name equals "test" as expected

    diagram.Model.AppendChild(node);

    // node.name now set to "1", unexpected

    node.Name = "test";

    // node.name STILL set to "1", unexpected

Thanks in advance for your help,

Mark

[Ramya Thirugnanam]

Hi Mark,  

 

Thanks for contacting Syncfusion support. 

  

Could you please check whether the same Name is assigned for multiple nodes? If yes, the node Name will be automatically changed, and the numeric value added to the name.  

For example: node Name is set as “test” for three nodes, then it will render as “test”, “test1” and “test2” respectively. It is the default behavior of our control.   

 

Regards, 

Ramya T 

[Mark Eborn]

Hello Ramya,

I checked, and the same Name is NOT being assigned to multiple nodes. Also, in my case, the nodes are getting renamed to "1", "2", "3", etc. after I append them to the diagram model, not "test1", "test2", "test3", etc.

What is stranger is that once they've been appended, I can no longer change the Name property of the nodes.

This was not the behavior in the last version I was using (15.4.0.17).  

Regards,

Mark

[Ramya Thirugnanam]

Hi Mark,  

 

We have used your code example in our application. We could not able to replicate an issue at our end. Could you please share us the modified the sample , customization of diagram class and video to represent or replicate the issue? This will help us to serve you better. 

 

Sample: https://www.syncfusion.com/downloads/support/directtrac/general/ze/nodenamesample1472938991  

 

Regards, 

Ramya T 

[Mark Eborn]

Hello Ramya,

I did some further testing and found that I can only reproduce the naming issues if I first call diagram.Model.Clear() or diagram.Model.RemoveAllChildren() prior to adding/appending all of the nodes. See the code snippet below:

using System;
using System.Drawing;
using System.Windows.Forms;
using Syncfusion.Windows.Forms.Diagram;
 
namespace WindowsFormsApp1
{
    public partial class Form1 : Form
    {
        public Form1()
        {
            InitializeComponent();
 
            LoadDiagram();
        }
 
        private void LoadDiagram()
        {
            // Calling either of these methods first causes the ControlNode naming issues
            diagram1.Model.Clear();
            //diagram1.Model.RemoveAllChildren();
 
            // Nodes are renamed "1", "2", "3" after appended, unexpected
            AddNode("49070");
            AddNode("49071");
            AddNode("49072");
       
            // Nodes are renamed "a1", "b1", "c1" after appended, also unexpected
            AddNode("a");
            AddNode("b");
            AddNode("c");
        }
 
        private void AddNode(string name)
        {
            var control = new Button();
 
            var rectBounds = new RectangleF(0, 0, 270, 170);
            var node = new ControlNode(control, rectBounds)
            {
                Name = name
            };
 
            Console.WriteLine("Node name before append: " + node.Name);
            diagram1.Model.AppendChild(node);
            Console.WriteLine("Node name after append: " + node.Name);
        }
    }
}

The console output is this:

Node name before append: 49070

Node name after append: 1

Node name before append: 49071

Node name after append: 2

Node name before append: 49072

Node name after append: 3

Node name before append: a

Node name after append: a1

Node name before append: b

Node name after append: b1

Node name before append: c

Node name after append: c1

Regards,

Mark

[Ramya Thirugnanam]

Hi Mark,  

Thanks for sharing details to replicate the issue. 

We can reproduce the issue. We have logged an issue report for it. The fix for this issue is estimated to be available on 26^th July 2019.  

 

Now, you can track the status of your request through the below feedback link. 

 

https://www.syncfusion.com/feedback/7625/node-name-has-set-as-wrongly-after-clear-and-add-the-node-into-the-model  

 

Regards, 

Ramya T 

[Ramya Thirugnanam]

Hi Mark,

The issue with “Node name has set as wrongly after clear and add the node into the Model" has been fixed and the patch for this fix can be downloaded from the following location.

Recommended approach - exe will perform automatic configuration
Please find the patch setup from below location:  

  http://syncfusion.com/Installs/support/patch/17.2.0.34/708457/F145993/SyncfusionPatch_17.2.0.34_708457_7262019045243872_F145993.exe  

Advanced approach – use only if you have specific needs and can directly replace existing assemblies for your build environment
Please find the patch assemblies alone from below location:  

  

http://syncfusion.com/Installs/support/patch/17.2.0.34/708457/F145993/SyncfusionPatch_17.2.0.34_708457_7262019045243872_F145993.zip 
   

NuGet Link:  

http://syncfusion.com/Installs/support/patch/17.2.0.34/708457/F145993/SyncfusionNuget_17.2.0.34_708457_7262019045243872_F145993.zip  

Assembly Version: 17.2.0.34
Installation Directions :
This patch should replace the files Syncfusion.Diagram.Base under the following folder.
$system drive:\ Files\Syncfusion\Essential Studio\$Version # \precompiledassemblies\$Version#\4.5
Eg : $system drive:\Program Files\Syncfusion\Essential Studio\17.2.0.34\precompiledassemblies\17.2.0.34\4.0

To automatically run the Assembly Manager, please check the Run assembly manager checkbox option while installing the patch. If this option is unchecked, the patch will replace the assemblies in precompiled assemblies’ folder only. Then, you will have to manually copy and paste them to the preferred location or you will have to run the Syncfusion Assembly Manager application (available from the Syncfusion Dashboard, installed as a shortcut in the Application menu) to re-install assemblies.

Note :
To change how you receive bug fixes, ask your license management portal admin to change your project’s patch delivery mode.

https://www.syncfusion.com/account/license

Disclaimer :
Please note that we have created this patch for version 17.2.0.34 specifically to resolve the following issue(s) reported in this/the Forum(s). 145993

If you have received other patches for the same version for other products, please apply all patches in the order received.

 

This fix will be included in our SP1 of Volume 2 which will be available in August 2019. 

 

Regards,  

Ramya T