>Of course they should know something about each other. The Cancel button knows it goes in the bottom left corner. The Ok button checks for an instance of PARENT.cmdCancel and if so, array itself with the same .Top property, just to the left by a required number of pixels. If on the other hand PARENT.cmdCancel doesn't exist then cmdOk goes to the bottom left corner. End of story.

Err, not quite. My example was where there are _four_ buttons, not just the standard OK/Cancel pair, which I agree could go in a container.

>You could have a mediator but in practice it's so slick to have objects recursively place themselves, so why bother.

I guess you've forgotten a discussion about a year ago that makes this one extremely ironic. No matter. :)