>No matter is right, because that's extreme nonsense. A year ago we were talking about keeping logically related objects concurrent in the face of events.

First, sorry to get you all riled up, Steve. I'll have you know that I'm not accustomed to talking extreme nonsense ("then for a beginner, you do it damn well!" --P.G. Wodehouse). :)

Buttons are not necessarily logically related, but they are spatially related. You haven't yet explained how you'd handle _four_ buttons. It seems to me that if you wouldn't want a textbox and a listbox to know about each other, you wouldn't want a Help and and Insert button to know about each other.

>This isn't an event-response situation, and it isn't even in any way an adaptive system. It's a one-shot layout task that, in this case, involves only the presentation layer; there it should remain, no?

I don't understand why a mediator should handle event-driven dependencies but not spatial ones.

>Or you could just code it in the form and object instances which, when you get right down to it, is exactly what you're doing with your mouse in the freaking form designer .

I think you've strayed from the subject at hand, Steve, which is how to handle multiple screen resolutions. There, it's not sufficient simply to slap controls down with a mouse.

> Nevermind.

As you wish. I sense an outbreak of the famous Blackian impatience and, as before, my tolerance for that is quite low.