>>>If I understand the way PropertyManager works you would have to write a container and bind to the container. The container would have one property for each property of the contained object that would raise the event. But, I could be wrong.

according to this article
http://www.bluevisionsoftware.com/WebSite/Books/CustomControlsAndDesigners/Samples/Chapter6.pdf

it seems that the PropertyManager is almost useless at this point...
:-/


>>Correct me if I am wrong but I think BindObject just wires up the eventhandler to the event source.

yeah, but in VFP that means we can also run some code when the property of an object gets changed, without the object ever knowing about it.


>>>The way I see the problem is that properties do not raise the propertychanged event in the first place because of performance considerations. They might not be needed in all cases so the component author did not raise the event so you have to fire the events yourself.

yeah, I hadn't think about the performance issue...