I haven't quite gotten to work, I'm guessing it's because of several
things: this isn't your full version, I'm actually implementing IList,
etc..
So I'm mix and matching derivatives and implementations to see what
happens; thanks for the assistance.
From what I've gathered from the debugger, it appears that, in the
above code example, when Button2 "Insert" is clicked, it calls
data.Insert(), which in turn raises OnListChanged, which then notifies
the DGV that a new item is being added, and so the DGV then calls
IBindingList.AddNew, which also raises OnListChanged, and it's on this
2nd OnListChanged that an exception is thrown.
I just added this note in case anyone else was trying to use the code
as a base to start from; like I mentioned in my previous post, there
are probably some pieces that were left out, in good intention, to
just address the particular issue of the WatchForChange function as
the means to mimic the native event handling of the BindingList<T>
object.
I'm just going to give in and use BindingList<T>.
Plus WPF, LINQ, and .Net 3 are probably going to obsolete this whole
approach anyway. It's so perfect how Microsoft releases platform
versions; .NET 10 probably exists right now, but they'll only release
it in increments to ensure that you pay top dollar to keep feeding
from their hands.
