I created a flowchart with two tables in it, and attached arrows to each of the nodes.

I set the chart's behavior to Modify and set the Locked property of each of the tables. When I then tried to move an arrow to another node in the second table, it would not move. I then removed the line of code that set Locked to true, and everything worked.

Is this a buglet or a feature? Is there some way to restrict modification of the contents, size, and location of a table while permitting arrows to be attached to node borders?

Also: I can't get cascading arrows to work at all. Any pointers there would also be helpful.

OK, setting EnableHandles to Handles.None works fine. Sorry to ask such simple questions.

As to cascading arrows: nothing happens. They just stay stuck to the node borders and will not move. I have created them like this:

Arrow arrow;
for(int i = 0; i < 10; i++)
{
       arrow = chart.CreateArrow(table1, i, table2, i);

       arrow.AllowMoveEnd = true;
       arrow.AllowMoveStart = false;
       arrow.ArrowHead = ArrowHead.Rhombus;
       arrow.CascadeOrientation = Orientation.Horizontal;
       arrow.Dynamic = true;
       arrow.SegmentCount = 2;
       arrow.SnapToNodeBorder = true;
       arrow.Style = ArrowStyle.Cascading;
}

I have verified that these properties are set for all arrows in the chart.Arrows collection. Nevertheless,
the arrows just stay stuck. If I change the Style to Polyline, the arrows are movable.

I would like arrows that can be moved up or down in a table and when they are moved they create a new vertical line segment when the endpoint moves. I think this is one use of cascading arrows, no?

That did it, thanks. I didn't even think about the endpoints co-inciding. I was thinking that when the segments were created that the distance that the arrow needed to traverse would have been split in half, and a segment generated for each half.

Everything works great now, thanks.