MDI child activation behavior

[KRH]

I posted this over in dotnet.framework.forms, but this is probably a better forum for it
Question: Why doesn't clicking anywhere on a child form (not just the title bar) in a MDI application activate the child in C#, as in VB.NET and almost any other Windows environment. Was this by design? I sure hope you don't need to call the form's Activate() event from the click event of the form and all of its controls, or is there another property of the form or parent to control this

This and a few other workarounds makes me wonder if C# is not the recommended Windows (form) application dev environment

Thanks
KRH

[Martin Stainsby]

"KRH" <an*******@discussions.microsoft.com> wrote in message
news:88**********************************@microsof t.com...

Question: Why doesn't clicking anywhere on a child form (not just the

title bar) in a MDI application activate the child in C#,

It does activate the Child forms in my C# MDI app --- VStudio 2003 pro. on
XP.

[KRH]

Thanks Martin. I am using VStudio Ent. 2003. I wonder what's the difference. Maybe just a setting
KRH

[Martin Stainsby]

"KRH" <an*******@discussions.microsoft.com> wrote in message
news:74**********************************@microsof t.com...

Thanks Martin. I am using VStudio Ent. 2003. I wonder what's the difference. Maybe just a setting. KRH

Have you tried it with a blank mdichild, it possibly could be a docked
component on the child form.
The mousewheel when clicked doesn't activate my mdichild although it still
works, I have to activate it through code. The normal mouse buttons are ok
though.