Hiya John


>Ah grasshopper, if you feel the code issue is relevant, then it should be the central part of your argument. Rather, the issue of re-use is basically what you are arguing below. If I need to write 10 lines of code or so - and know that I will not re-use the object, I will not make a class. As far as custom properties go, that by itself is not an argument to make a class.
>
>Also, creating a class does not necessarily mean adding another level to the class hierarchy. After all, it could be a sibling class.
>


Yes, Master. No, really, I think we're saying the same thing.



>>I think the quantity of code *is* relevent when you examine the use of the new >class. If you need the custom properties or behavior more than once or twice >then you are 100% correct. But if this is a one-shot modification to a >control, making a whole new class makes it harder to maintain because that's >adding one more level of tracing to debug.
>
>>Just my .02