Hi,

Custom object's notify the UI differently then custom lists.

In NET1.1, custom object's fire a "PropName+Changed" event and in NET2.0
custom object's can fire INotifyPropertyChanged.PropertyChanged.

In NET1.1, custom lists must implement IBindingList and fire
IBindingList.ListChanged when one of its items have changed.  This means you
need to implement this yourself, eg. make it so that the custom objects know
which custom list they belong to, then when one of the object's properties
changes, the object calls a method on the custom list which will fire
IBindingList.ListChanged(ItemChanged).

The same is true for NET2.0, BUT you can use BindingList<T> as a custom list
or as a basis for a custom list.  A BindingList<T> will catch the
INotifyPropertyChanged.PropertyChanged fired by any of it's objects and then
fire IBindingList.ListChanged (resulting in a correct update of UI).

Example (NET2.0)

public class CustomObject : INotifyPropertyChanged
{
 private string name;
 public PropertyChangedHandler PropertyChanged;

 public string Name
 {
   get { return name; }
   set
   {
     if ( name != value )
     {
       name = value;
       if ( PropertyChanged!=null)
        PropertyChanged(this, new PropertyChangedEventArgs("Name");
     }
   }
 }
}

public class CustomList : BindingList<CustomObject>
{
   // The BindingList implements IBindingList and will fire
   // IBindingList.ListChanged when one of the items
   // fired INotifyPropertyChanged.PropertyChanged.
   // It also includes typical typed collection methods.
}

CustomList cl = new CustomList();

cl.Add ....
cl.Add....

txtMyControl.DataBindings.Add("Text", cl, "Name");

HTH,
Greetings