>>Yeah, that makes sense, but doesn't seem to buy anything over simply writing the programmatic resize code as:
>>
>>

>>LOCAL nAnchor
>>
>>nAnchor = Whatever.Anchor
>>Whatever.Anchor = 0
>>
>>* do the resize/reposition
>>
>>Whatever.Anchor = m.nAnchor
>>

>>
>>What I was looking for was a way to not have to remember to do something (whatever it is) on a programmatic resize/reposition.
>>
>
>Yeah, but then why use anchors, if they're going to be 0 during the resize? My suggestion was based on the assumption that you'd raise an event like BeforeProgramaticResize which the objects would react to, by deAnchoring themselves.
>Or, maybe I misunderstood it. I was assuming that you'd want to deAnchor the objects before the programatic resize and reanchor them after so they would behave properly to the interactive. Are these objects supposed to react to the progr resize or is only their form/container affected by the programatic resize?

I've obviously done a poor job of explaining the problem everywhere I've posted. Here's the deal. I'm modeling a physical object, which the user can construct interactively.

When the form is created, I programmatically resize it and add and position a number of objects.

Once the form is displayed, the user can:
1) add objects, which must be programmatically positioned correctly;
2) move objects around, which must be properly repositioned programmatically;
3) resize the form, in which case everything must be resized and repositioned.

The anchors handle #3, but get in the way of #1 and #2.

IAC, I've added code like that I showed above and it's all working. I just hoped to make it more transparent.

Tamar