Not sure if this is a bug or something I'm doing wrong....

I have two TableNode instances, multiple rows in each TableNode. I have DiagramLink's between rows in the two TableNodes.

In my UI, I use a right-click context menu to invoke functionality to delete a row from one table.

Step 1 is to enumerate all DiagramLinks between the selected row and any other row in any other table (this is both outgoing and incoming links)

Step 2 is to call IncomingLinks.Clear() and OutgoingLinks.Clear() for the selected row in the specific TableNode

Step 3 is to actually remove the previously enumerated diagram links

Step 4 is to actually remove the selected row from the specified TableNode.
I've tried TableNode.Rows.RemoveAt(), TableNode.Rows.Remove(), and both function calls cause the stack overflow condition to occur.

I even thought that the problem was caused by one thread attempting to update the TableNode outside the UI thread, even though there was no sign of that particular error message; I moved the row deletion code to a delegate and invoked it from Dispatcher.BeginInvoke(....). Same error occurs.

Any thoughts?

Yep, we very much want to add support for directly adding and removing objects from the Rows, Columns, ControlPoitns, etc. collections; only if we had a couple of weeks free from urgent requests to do this ...