Click Even In C# MDI Form

Question

0.00/5 (No votes)

See more:

C#

Dear all i create one application in VS2008 C#. I use mdi form click event but it will not work. any one help me plz...

Posted 15-Jan-13 21:12pm

abdul kamaal naser

Add a Solution

Comments

CHill60 16-Jan-13 4:13am

What doesn't work? Post your code for the event and say what it is that doesn't work and/or which line the problem is on

dan!sh 16-Jan-13 4:27am

You need to be descriptive here. It's not easy to understand the question based on your post.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

BillWoodruff · Answer 1 · 2013-01-17T06:16:00

I am pretty sure that you are confusing the MDIForm container window, itself, to which you can assign certain interaction (Mouse) Events: but, those Events will never be triggered.

When you create a WinForm Project, and set the IsMDIContainer Property of the main (start-up) Form to 'true: it becomes a really different type of "animal" than a regular Windows Form.

You can wire-up mouse-related EventHandlers to the MDIForm: like: Click, MouseDown, Leave, MouseClick, MouseMove, Enter: none of those Events will be triggered. Note: I consider the fact you can assign EventHandlers to an MDIContainerForm in the design-time Visual Studio PropertyGrid a serious design flaw: in my opinion, those Events should never appear in the PropertyGrid for an MDIContainerForm.

However, you can assign Keyboard EventHandlers: if you set the MDIContainerForm's KeyPreview Property to 'true: you can write EventHandlers for Events like 'KeyDown: and they will be triggered.

The whole idea (if it ever was other than a "kludge") of MDI architecture was: end-users interacted with MDI ChildForms, not with their "Parent" Form turned into an MDIContainer !

By the way, MDI is now a kind of old "fossil," and it's butt-ugly as user-interfaces go, and it's deprecated by Microsoft.

There are better ways of handling multiple Forms/Windows !