Formally,
Form, as any
Control has a focus, but this property is not actual for this type of
Control. The actual property is the
activation. The MDI weirdness is: the parent one one of the child forms are activated at the same time. Still, the notion of
focus is applicable to one of the control on each form, which gets focus when its form is activated. I don't see why it can cause a problem. Hopefully, these consideration can help you to put it right. As to the MDI itself…
Here is the idea: who needs MDI, ever? Why torturing yourself and scaring off your users?
Do yourself a great favor: do not use MDI at all. You can do much easier to implement design without it, with much better quality. MDI is highly discouraged even by Microsoft, in fact, Microsoft dropped it out of WPF and will hardly support it. More importantly, you will scare off all your users if you use MDI. Just don't. Please see:
http://en.wikipedia.org/wiki/Multiple_document_interface#Disadvantages[
^],
How to Create MDI Parent Window in WPF?[
^].
I can explain what to do instead. Please see my past answers:
Why MDI form is not supported natively in WPF ?[
^],
How to Create MDI Parent Window in WPF? [
Solution 2],
Question on using MDI windows in WPF[
^],
MDIContainer giving error[
^],
How to set child forms maximized, last childform minimized[
^].
—SA
Submit an article or tip