>Here is some code from my resizer's ResizeControls method that I use to resize my forms. It handles grids just fine:
>

Hi Marcia-

I am replying to you, but the question is really for everyone in the thread.

I am curious- is the behavior like that given by the code Marcia posted, and the behaviour of the Resizer class in the FFC really what ya'll wanted in a resizer class?

I have never seen a commercial application that actually resized and moved buttons and the like when the form was resized. Have ya'll? Some of these classes are even changing the font sizes on controls. This is completely non-standard behavior.

From my experience, when a user wants to resize a screen, it's because she wants to see more text in an edit box, more lines or columns in a grid, or more items in a listbox, treeview, etc. When a form is resized, a button that was on bottom and right of the form should stay on the bottom and right, and a button on the top left should stay on the top right, and stay the same size; the new form real estate should be occupied only by controls who can really use it, not by controls like command buttons and labels that have just expanded themselves to take up more room. Buttons, textboxes, labels checkboxes, combos, options groups should not resize, they should float. Grids, pageframes, editboxes, listboxes should resize.

The only way that I know of to acheive intelligent resizing behavior is to add properties to every base class control that let you specify at design time whether the control should float or resize. A form method called from the Form.Resize event should know what to do with each control only after looking at these custom properties.