Fabio,

How would Form/Class designer to know what you intention is when you change the size of a form? Maybe you are increasing size of the form to add a column or row of the controls?

>Anchor have a sufficient implementation at Runtime,
>and it can to be extended without many problems;
>but at design time the situation is critical.
>
>If you design a visual class/form with 50-1000 members,
>and configure the members tree structure with a complex
>Anchor schema,
>if, after, you change the visual class/object size,
>or put it like member of another class/form and resize
>it at design time, THE ANCHOR SETTING IS LOST !!!
>This occur because the greater part of the configuration of Anchor
>makes reference to two not present values in the definition of an visual object:
>Right and Bottom.
>
>An simple example is:
>A Pageframe, with N pages,
>you add the N+1 page and this must to have a great size,
>when you resize the pageframe,
>the N pages lost the Anchor setting!
>
>With current situation,
>the usefullness of Anchor remarkablly is reduced.
>
>The solution is very simple:
>The Class Designer have to apply the Anchor setting,
>and Move() the members like at runtime!
>