IIRC, the explanation given way back when is that forms in the form designer are actually a subclass. Controls on the form are instances.

I agree with you that it would be a nice feature, but instances behave differently than class definitions.


>I should clarify something, I understand protyping isn't where you should be doing your class design, but I still don't see the harm in being able to add properties and methods to classes through the form designer and then being able to do a "save as class..."
>
>
>
>>Can someone clue me in. When working in the form designer, you can add properties and methods to the form through the "form" menu pad option, but you can't do the same for objects contained within the form. You have to first save the contained objects to a class, get out of the form, then go through the class designer to add custom properties and methods. I'm just wondering how come custom properties and methods can't be added to contained objects through the form designer. Is it because it would foster bad design?
>>
>>It seems to me building quick prototypes would go much faster if this capability existed in the form designer. Or is my thought process just a??-backwards