>Erik,
>
>Good points, as usual the response here has been great!
>
>After reviewing the information provided and poking around in various class libraries I have decided upon this approach. I will create a sizer class that will move the controls to their new locations. But, it will move each control according to the desired behavior of the control(property within the control).
>
>I just couldn't see myself maintaing the same (or simular) code across several classes, but the idea of allowing the control to behave differently is great.
>
>
>...tim

Before you decide to delegate this task to another object, you will want to consider and test the performance cost of delagating this task. I agree, a single place for this code would be better, but I started out with a similat approach and ended up going with the way I went because it was considerable faster. This is a touchy performance area, delays can cause goofy looking resize/stretch efforts.

BTW, maintenance has not been an issue- there are exactly 2 lines of code in each Resize method, and two in the Float method, these are in addition to the 2 or 4 in each init method that store size/position information.