We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. Image for the cookie policy date

Swimlane acting like a connectable node, was working ok with old SDK


I just upgraded to the latest SDK to take advantage of the fix for resizing adjacent swimlanes, but I noticed a peculiar problem:

The swimlane has now become a connectable target. It was working in an early release of the SDK. Any ideas why this is happening?

This is what I am adding to my palette:

   private Lane CreateSwimLane(string name, string orientation, int width, int height)
            var swimLane = new Lane
                AddInfo = new Dictionary<string, object> { ["type"] = name },
                Name = name.Replace(" ", ""),
                Header =
                    Text = "",
                    Width = 60,
                    Height = 60,
                    FillColor = "#C7D4DF",
                    FontSize = 11
                Width = width,
                Height = height,
                Orientation = orientation,
                FillColor = "#f5f5f5",
                OffsetX = width / 2,
                OffsetY = height / 2
            swimLane.Constraints |= NodeConstraints.Resize;
            return swimLane;



Attachment: Capture_5c4e5eb9.zip

2 Replies

AS Ajay Soni January 11, 2017 10:28 PM UTC

FYI tried removing this constraint, but didn't work:
swimLane.Constraints &= ~NodeConstraints.Connect;

SG Shyam G Syncfusion Team January 12, 2017 12:12 PM UTC

Hi Ajay, 
We considered this “Connector should not be connected with the swim lane” as an issue and a support incident has been created under your account to track the status of this requirement. Please log on to our support website to check for further updates. 
Shyam G 

Live Chat Icon For mobile
Up arrow icon