>hmm... I'll keep that in mind then... anyway, that makes me wonder: let's say I'm using an object written or provided by someone else, and this object doesn't raise events when a property is changed... this object has been written by someone else and I have no access to its source code.
>

Well, this would be exactly the case for the built-in .net framework components!

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.


>Wouldn't it be possible for me to hook in that object's property in the way I could do with VFP's BindEvent function? as in
>
>

>BindObject(myObject, "myProperty", myHandler, "myMethodHandler")
>

Correct me if I am wrong but I think BindObject just wires up the eventhandler to the event source. 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.