Hi Erik

>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?

Haven't seen Marcia's code, but the FFC resizer class may be alright under certain circumstances.

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

This is what my resizer class does, but I have the option to limit the behavior to changes in screen resolution as opposed to allowing the behavior when a user resizes the form. Keep in mind that resizing for screen resolution is a different animal: In effect, the user is experiencing the UI as if you developed in that (the user's) screen resolution.

You and I have discussed this before (with Bruce C. I think).

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

I agree. This is the circumstance I was referring to above. In my case, this would justify a second resizing scheme (in addition to the one for screen resolutions) - something which I have been pondering for awhile.

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

Absolutely.