How to dismiss the msg box for any click on the msg box?

Question

3.00/5 (2 votes)

See more:

VS2008

Visual-Studio

I want to dismiss the message box for any click on the message box. Please help me with this.

Posted 19-May-11 21:42pm

bunathangaraj

Add a Solution

Comments

Sergey Alexandrovich Kryukov 20-May-11 4:37am

There is not such language or platform as VS2008! Tag it all!
--SA

4 solutions

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)

CS2011 · Answer 1 · 2011-05-19T22:19:00

Solution 2

There is no simple way to do it (I am talking about winforms here as there is no tag in the qustion I am not sure what’s the question is related to). You will have to write custom control to achieve that.

Posted 19-May-11 22:19pm

CS2011

Comments

Tarun.K.S 20-May-11 6:21am

Like creating a Custom Window instead of MessageBox, and then handling its MouseDown event to close the window. Am I right?

CS2011 20-May-11 6:55am

Hit the nail on the head. Absolutely correct.

Tarun.K.S 20-May-11 7:22am

Thanks! 5d

Sergey Alexandrovich Kryukov · Answer 2 · 2011-05-19T22:38:00

Solution 3

Yes, you can easily do it. Never do it! Don't make your user mad. Message box is message box, not after you implement a "feature" like that.

—SA

Posted 19-May-11 22:38pm

Sergey Alexandrovich Kryukov

Comments

Tarun.K.S 20-May-11 6:20am

It's a requirement SA which the OP wants to implement.

Sergey Alexandrovich Kryukov 20-May-11 23:46pm

Why do you think requirement is an excuse?! Tomorrow your manager will send you the requirement to rob a bank. When police arrests to you, will you excuse that it was a requirement work. That manager will say that is was a result of typo, and that you were supposed to give him feedback and point out the problem instead of actually robbing the bank. You will go to prison.

Programming is exact same thing.
--SA

Tarun.K.S 21-May-11 14:03pm

I must say the example of yours is very less practical.

Sergey Alexandrovich Kryukov 22-May-11 2:13am

About robbing the bank? Sure, not robbing the bank is quite a practical way not to go to prison. :-)
--SA

Albert Holguin 20-May-11 10:35am

lol, SA is right, this sounds like building in a bug intentionally!

Sergey Alexandrovich Kryukov 20-May-11 23:48pm

Thank you, Albert. Please see my comment below.
Requirement document is no different from other engineering artifacts. It can also have bugs.
--SA

Albert Holguin 21-May-11 11:21am

MY 5!

Sergey Alexandrovich Kryukov 21-May-11 21:32pm

Thank you, Albert.
--SA

Albert Holguin 22-May-11 16:37pm

You're comment about the requirement document possibly having bugs as well is very, very true! I was a systems engineer in a past life and its easy to make mistakes with details when you're writing large specification documents.

Sergey Alexandrovich Kryukov 22-May-11 17:38pm

Better work is not the one that has no mistakes at all, but the one where those mistakes cost less.
--SA

Albert Holguin · Answer 3 · 2011-05-20T04:38:00

Solution 4

If this is MFC based, you can just intercept the messages going to the dialog and dismiss it when you catch the messages that you want to trigger this effect (mouse down and you may think of others), but I do agree with SA, this doesn't seem like a desirable effect at all.

Posted 20-May-11 4:38am

Albert Holguin

Comments

Sergey Alexandrovich Kryukov 20-May-11 23:49pm

With the last note it make sense, my 5 :-)
--SA

Albert Holguin 21-May-11 11:21am

lol... its an odd "feature"

Sergey Alexandrovich Kryukov 22-May-11 2:10am

Don't you think this is way too typical for questions we see here: some people very uncomfortable with very basic programming chores requesting for hard-to-implement "features" designed to make potential users mad?
--SA

Albert Holguin 22-May-11 16:41pm

Definitely. Seems to be a common goal of new developers to annoy users.

Sergey Alexandrovich Kryukov 22-May-11 17:40pm

I would not mind to get annoyed at first if my response can help and if the help is understood and used to improve things.
--SA

Joan M · Answer 4 · 2011-05-19T21:58:00

well...
typically when you press a button in the messagebox it disappears returning the value of the button you've pressed... you'll have to decide how to process that value once it has reached again your program flow...

Tipically (in pseudocode):

A = MessageBox(...)
switch (A)
{
  case...
}

So it is up to you to dismiss it or not...

In fact if you call only messagebox without assigning it's return to a variable then nothing will happen apart of the MessageBox disappearing.

OOps!

re-read your question...

Messagebox is an api, you can't subclass it... you should replicate a dialog that look like a messagebox and put your functionality there...

Look here: http://www.codeproject.com/Messages/938953/How-can-I-subclass-MessageBox.aspx[^]

Anyway take a look here also : http://www.codeguru.com/cpp/w-p/win32/messagebox/article.php/c14605[^]

HTH...

How to dismiss the msg box for any click on the msg box?

4 solutions

Solution 2

Solution 3

Solution 4

Solution 1

Add your solution here

Preview 0

Existing Members

...or Join us