Focus Problems with MDI child forms

  • Thread starter Thread starter Trev Hunter
  • Start date Start date
T

Trev Hunter

Hi Folks,

Sorry if you have seen this post before - I've posted it before, but it
seems to have gotten lost in Outlook limbo - it's visible on the web
interface, but not in any news reader I've tried :S

A while ago, I came accross this post by Armin describing how to reporduce a
focus bug with MDI children. I am currently experiencing the same problem in
my application although I'm not using an ActiveX control directly on the
form as in Armin's example (my 3rd party toolbars and menus could be the
culprits though).

I'm using Visual Studio 2003 with .net 1.1 on Windows XP.

Any help would be greatly appreciated.

Trev.

Origional Post by Armin (edited) - see http://tinyurl.com/2ezw2 for
origional:
 
Hi Trev,

Is there a reason you did not include the newsgroup

microsoft.public.dotnet.languages.vb in it,

that is the group where Armin is the most active from the international
groups, but not in the ones you have included I thought.

And as far as I have seen in the newsgroup is Armin in the newsgroups one of
the real MDI experts.

If you even want to have more success you can ask it also in the German
language in the newsgroup

microsoft.de.german.entwickler.dotnet.vb

Cor
 
Cor,

I didn't post it to the VB group because I thought it was a more generic
problem (hence the .windowsforms group). I added the .faq and .general
groups because I was having problems with the .windowsforms group and was
hoping for a better response. Surely someone else out there has come accross
this problem before? I'll do up a sample project and see if it is limited to
VB.
that is the group where Armin is the most active
Click to expand...

Thanks for the tip about Armin's whereabouts ;) He's the one who posted the
original article a while back, but there was no responses to that. Next time
I see him in a group, I'll discretely OT the thread and ask him.
If you even want to have more success you
can ask it also in the German
language in the newsgroup
Click to expand...

Unfortunately I can't speak German - only English, VB and passable C# ;)

Thanks again for the tip,

Trev.
 
Hi Trev,

Thanks for letting us know this issue,
I was successfully reproduced it follow the steps. I'm contacting the
product group and let them take a look at it, I'd appreciate your patience
while we investigating this issue,
Thanks for your understanding!
Best regards,

Ying-Shen Yu [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.
This mail should not be replied directly, "online" should be removed before
sending.
 
Thanks for investigating this for me. I'll post here if I come accross any
more information regarding this issue.

Best Regards,


Trev.
 
Hi Trev,
I apologize for the long delay,
I have confirmed this issue with our product group.

The native mdi form does not seem to get the WM_ACTIVATE message, but it
gets the WM_MOUSEACTIVATE message. We may create a derived form for MDI
Child Forms and override the WndProc like the following code snippet to
work around this issue.

<code>
protected override void WndProc(ref Message m)
{
switch(m.Msg)
{
case 0x21: // WM_MOUSEACTIVATE
this.Activate();
base.WndProc(ref m);
break;

default:
base.WndProc(ref m);
break;
}
}
</code>

Thanks!


Best regards,

Ying-Shen Yu [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

This posting is provided "AS IS" with no warranties and confers no rights.
This mail should not be replied directly, "online" should be removed before
sending.
 
Thanks for the help. I used your code by implementing a base class for all
my MDI child forms to inherit from and overriding the WndProc method in the
base class.

Thanks again,

Trev.
 
Back
Top