|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Validation in MDI children toggledThe following "event-map" shows the behaviour. First I open an MDI, and activates a control with a Validate-event: Form-Enter - Load Control-Enter Then I open another MDI (only events for the first MDI/control is shown): Control-Leave Form-Leave Control-Validating - Validated Then I "toggle" back to the first MDI via an MDI-menu, and presses "Tab" from the control that should be validateted: Form-Enter The control is a TextBox, and of course CausesValidation is true. Then I close the form: Form-Closing - Leave As one can see, when toggling from one MDI to another, the active control on the second MDI does not seem to get focused, and i.e. is not validated. Any suggestions??? I forgot to mention, this behaviour seems to have arrived after installing
the Framework 1.1 SP1. Any help would be highly appreciated! Show quote "spawner" <spaw***@discussions.microsoft.com> skrev i melding news:06F5E55D-8E48-4909-B9CE-2C001223D797@microsoft.com... > Having an app with several MDI children, a strange behaviour mindboggles > me. > The following "event-map" shows the behaviour. > First I open an MDI, and activates a control with a Validate-event: > Form-Enter - Load > Control-Enter > Then I open another MDI (only events for the first MDI/control is shown): > Control-Leave > Form-Leave > Control-Validating - Validated > Then I "toggle" back to the first MDI via an MDI-menu, and presses "Tab" > from the control that should be validateted: > Form-Enter > The control is a TextBox, and of course CausesValidation is true. > Then I close the form: > Form-Closing - Leave > As one can see, when toggling from one MDI to another, the active control > on > the second MDI does not seem to get focused, and i.e. is not validated. > > Any suggestions??? |
|||||||||||||||||||||||