>Nadya,
>
>When I'm building composite containers like this I always put code in the class to resize everything based on how big the container was stretched to on the design surface. It does this at runtime. It may look a little "odd" at design time because the internal objects are sized/positioned according to the designed size of the container. It really doesn't take that much code to make it work. The same code can be called from the Resize event to handle a user form resize event. Although I'll typically have a form minimum size in place to prevent UI oddities *s*.


David,

Yes, this is exactly what I meant. This simple Resize method should be in this class. I wrote a message to out team members about these two little enhancements (which, in my opinion, should be there from the first place), but I was just ignored by the person, who is responsible for our classes, and my manager told me, that we're not going to change them, though I tried to convince him, why it's important. His reasoning was something like: how many times you're going to design this form, adjust listboxes once and that would be it. I'm not that good in arguing, so he just remains with his original opinion. On the next day, he told me, that we have to find out a way to have a positive discussion...

Well, I'm a little tired of all these minor, but important problems, which nobody except me cares about. If I would be responsible for classes changes, I would make them long time ago. But since I'm not, I have to write letters about each problem found, which are either ignored, or had a response such: "Yes, good idea, but we would not deal with it now...". That means, we would not deal with this problem at all...

Thanks again.