>But what if some of those objects are conrols themselves?
As the control class builds an outer rim to your inner structure and user defined properties and methods will be added at that level, each of your controls will work as if some native control with no visible inner structure.

So this will work. As you can bind events of native controls to events of other native controls you can also do so with several of your self defined controls, even within a self defined control. Of course youd first define each control individually as a class and then compose the final class out of these.

You just can't bind some inner object of YOUR_CONTROL to some inner object of YOUR_OTHER_CONTROL directly. But you'd be able to bind to methods or properties of eg your TITLE_BAR and this method could then forward anything to the inner structure of itself and vice versa. You may like to use properties defined with access and assign methods (there you have OO "fields" as far as VFP can simulate these).

>SETALL()...at least to me, I probably wouldn't use it anyway.
As you are concerned with other developers using your control you cannot really turn that problem down as you can't forbid them to use SETALL(). But as there is no better alternative we can live with that small gap.

Bye, Olaf.