Is there a message map to windows forms application?

Question

1.00/5 (1 vote)

See more:

The windows forms application code automatically generated by Visual studio c++ looks very different from those for dialog or MFC applications.

How can I add message handling to Windows forms applications? I would like to start another thread, listen for message that the thread is finished, then do something. I'm not sure how to get started from the code like:

C#

Application::Run(gcnew Form1());

which does not tell me about the message handling mechanism.

What I have tried:

searched online for example code. MSDN documentation on windows forms points to .net framework. Don't know whether I need to jump into reading extensive information about.net framework for what I need to do.

Posted 13-Feb-16 6:15am

Member 4243997

Add a Solution

Comments

Sergey Alexandrovich Kryukov 13-Feb-16 21:28pm

What do you mean by "message"? A regular Windows messages? They are already encapsulated into System::Windows::Forms; you don't need to use them directly. And how about reading original MSDN documentation? It looks like you are trying to get all by guess, using some Quick Help. Better don't waste your and our time; first learn essential background, then ask your questions.
—SA

Philippe Mori 13-Feb-16 22:07pm

In .NET, you rarely need to directly use Windows messages or interact with the message loop. Common messages already have event handler for them. You just have to attach a function to the event handler for whatever event you want to respond.

Usually, you don't uses Windows message directly to communicate with a thread. In .NET, you have a background work, Thread class and async programming amoung other and thus, it is preferable to use them properly.

MFC is an old technology. .NET is far more easier to use. As such, for common things like multithreading or message handling, better to use what .NET offer and only rely on low-level stuff if you really need.

2 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)

nv3 · Accepted Answer · 2016-02-13T06:32:00

Message handling in .net is done primarily by registering a message function with the control. The mechanism used for that is called "delegates". In comparison with the old MFC message maps this is very elegant.

To get a start on this, just download one of the many examples of a small GUI program in C++/CLI or C# and you will quickly see how it is done.

Dave Kreskowiak · Accepted Answer · 2016-02-13T07:21:00

Solution 2

There is no message that says "a thread is finished". The thread either dies quietly when its work is done or the thread is responsible for signalling other code that cares. There are quite a number of ways to do this, but listening to the message pump is not one of them.

Posted 13-Feb-16 7:21am

Dave Kreskowiak