It is already the minimum size to begin with. It can be made bigger, but not smaller because I didn't want to get into the issue of changing the font size at this time.

In order for the end user to get this, I would have to size the control smaller, which is quite obvious visually, and then completely ignore the fact that there is a big red message telling me the control is too small. I'm not that stupid. :)

So far, no one has suggested a viable alternative. I don't want it to automatically make itself bigger because I want to control the size. I don't want it to just not instantiate because then there's a blank spot on the form with no indication as to why.

I am absolutely amazed that you guys are fighting this so hard. I don't see what is so wrong about writing myself a little note if I somehow miss the fact that I made the dang thing too small. It's not like it's even likely to happen. I can see at design time if it's too small.

Michelle


>Whenever I've done this sort of thing the composite control has a certain "as-designed" minimum size. When I drop it onto the place I want to use it I can see at design time how big a place it needs. Sometimes these kinds of controls are designed to adjust their size to fit the container size. For example I have a generic thermometer class, that's designed with a 100 pixel wide thermometer. If the class as used is dragged out to be 500 pixels wide the things adjust themselves to the bigger size.
>
>Having this kind of developer message laying around in your code, allows at least a small chance, that it won't adequately be tested and might just pop up on the end user.