>>I don't see a corresponding event that fires when the container deactivates.
>
>UIEnable handles both the enable and disable. It passes a parameter telling you if its going or coming (goes against the rest of the event model, but hey)
>
DOH!
>>It also doesn't fire the first time the page is activated if it happens as a result of the form's initial activation.
>
>True, but easy to fix (my pageframe does a UIEnable on the first page at startup anyway)
Then there's the philospohical argument of who knows what the default action for the page's content should be. Is the container 'aware' of which member of its content should have the default, or should the control assert its 'defaultdom'? I'd tend to believe that the control doesn't know enough - there might be several controls that might be valid default actions depending on the context of operation - for exampe, if you have an edit/non-edit state distinction, when in 'edit mode', the Save button might be the default, while if non editing, either the 'Add' or 'Edit' button is the default. The container in this case would be aware of the state, and ought to be the one telling a given control to assume the default mantle.
