Well, do you want me to create a patch? I and many other users are using NH with WPF which REQUIRES all collections to be observable. In order for us to be able to use the trunk, the bare minimum is add this template method to AbstractPersistentCollection: protected abstract void OnCollectionChanged ( NotifyCollectionChangedAction action, object changedItem, int index ); and then call it from all of its subclasses, whenever the collection's contents are modified. With that in place, then I could take care of the rest in my updated ObservableCollections project. Making that change to AbstractPersistentCollection would not in any way adversely affect other uses of persistent collections.
On Nov 26, 9:29 pm, "Fabio Maulo" <[EMAIL PROTECTED]> wrote: > 2008/11/26 HappyNomad <[EMAIL PROTECTED]> > > > > > NH 2.1 targets .NET 3.5, and > > observability is a fundamental feature of .NET 3.x, so I think the > > best way to solve this problem is to incorporate observability into > > the NH core. > > Sure... and sure we will add INotifyProperyChanged, and a base class to work > with lazy-loading and INotifyCollectionChanged and probably IBindingList > implementation. > Be sure about that. > -- > Fabio Maulo
