>Paul,
>
>>So, I wouldn't worry about the performance hit unless you've got a huge amount of code firing for every event.
>
>Thank you very much for your reply! How do you currently deal with your own extensions to the MM base classes?
>
>Armin

I haven't run into too many instances where I've needed to do this yet. The composite classes used in the framework have been generic enough that any modifications to controls could easily be handled by subclassing the existing controls and just using them on the forms. That is, the built-in forms generally only have buttons on them and I don't change button behavior very often. In the cases where I wanted to change the grid behavior or something along those lines I just created my own form instead of subclassing an existing one.

In the case of my resizer class, I wrote a simple applet that runs through the classes listed in a table and can automatically add the necessary properties and methods to them. I was planning on running this against the cControls library directly. If any framework updates came around I could just rerun this applet.