So far, no one has shown me something that "wouldn't surface in the runtime environment". It seems my options are as follows:

1. Don't init the control at all, leaving a blank spot on the form.
2. Resize the control automatically, possibly covering other stuff on the form.
3. Use ASSERT to send a message to the debugger that something's wrong with the control. (And do _what_ with the control itself? I don't remember you mentioning that)
4. Put a placeholder in place of the control with a message explaining why it didn't init.

I like #4. So does Microsoft, evidentally. In Internet Explorer, if a picture doesn't load, it puts a placeholder with an "x" in it to let you know there should be something there.

All this arguing has failed to convince me that there is something wrong with my approach. Every method suggested has a visible effect to the client, if I'm dumb enough to give it to them with the control too small. Since that is entirely under my control, it will not happen.

Michelle



>Michelle, if it doesn't make sense to you, far be it from me to suggest something as nonsensical as building in development-mode debugging and error trapping that wouldn't surface in the runtime environment. You're much better off doing what you think is best; what works for me is not what may work for you.