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*.

>Actually, I just listed important features, they are not ranked this way. But in my opinion, it's important to have resize for this particular container class. Right now if I drop this class on my form, I have to manually adjust listboxes and buttons, etc. to make them look right, or I prefer to write a simple code, which will correctly position buttons, labels and listboxes inside this container. I'm not talking about form's resizing feature. I believe, we have a custom class, which is part of our baseform, but the code of it is never executed, besides our forms don't have resize abilty anyway :( This auto-resizing may be a feature, controlled by some logical property, but at least, code should be available. The code itself is simple and may be just taken from _FFC _mover class.