Surely this would be better achieved with some kind of custom container for buttons?
Possibly. But what if you want to create a button that has the "right" minimum dimensions and you want to put it in a container with other non-button components? I think this is a pretty valid use case - the current approach supports it, whereas a custom button container would not.
Also, as you have probably seen, we try very hard to stay away from "special case" scenarios like this. That makes me even more reluctant to consider adding such a container.
Which would make a good place to put things like the logic for determining the correct platform order of OK and CANCEL buttons.
I'm not sure how (or if) we'll try to tackle that. Alerts and Prompts don't have any built-in buttons - they are all user-specified. The file dialog I'm working on right now does have OK and Cancel buttons, but I'm planning (for now) to use Windows conventions.
Pivot is a UI toolkit unto itself, after all, so we can theoretically dispense with platform considerations here. But it is definitely worth thinking about some more.
G
