>Paul,
>
>>I'd probably need/want something like this for the cContrls library, an I-Layer class that cForms::cBaseForm inherits from (instead of a base form), plus a few of the kCustCtl classes.
>
>It was me, who brought up the topic lately <g>. I've solved the issue for me with Hooks. (I think you pointed me to that!?)

Yeah, I thought this came up recently ;-) Now I remember...

>This way, the hooks can be sublassed anyway I want (for different projects, clients, etc), but I still have to modify the MM control classes. This is, where an I-Layer would still be helpfull. I could then implement my interface to the hook collection in the I-Layer.

This is the main reason I'd want one. Most of the changes I've done can be easily handled through subclasses. But there are a few others that would require changes to the MM classes. In some cases, I've gone ahead and done that, but I know this is going to bite me on the next upgrade.