So I have the table node and it has multiple rows each corresponding to a property. I am using the feature that was just added to creat/destroy edit control whenever a user clicks on a cell in the right hand column.

The thing is the example originally given for this has one text box for all table nodes. It does this I presume to remain lightweight. The problem is it becomes insanely convoluted to handle the events because you have a gigantic event handler that has to check state of other things.

I am simply thinking that each table node will have a different combobox/textbox for each property, with its own event handler. So I may have 50 instances of the same table node, each with 8 properties. I will therefore have 400 control instances (text boxes, combos, whatever). But I am thinking this will still be relatively lightweight in terms of painting because only 1 of the 400 will ever be visible at once, the rest will be hidden until their corresponding cell is clicked on.

So this is sort of a compromise. Do people agree that this is a decent compromise in terms of trading off a bit more sanity in event handling in exchange for some additional overhead?

5000 would be far more than I would have in my application instance. If it ever came to that I could revert to single controls. Thanks for the feedback!