Timer issues in mfc VC++ 6.0

Question

0.00/5 (No votes)

See more:

I am adding code in already proven code which is connected to instrument thru ethernet.i am adding another instrument API in the same code.i want to generate signal for every 50ms to achieve that time I am using for loop to generate signal for different Frequency used sleep for 50ms. When I run the code the whole application is hanged up to completion of for loop. I want to generate Frequency signal for every 50ms without hanging application. I have two ideas one is timer and another is thread.

What I have tried:

I have tired with timer but is not worked. Any dialog based thread generation examples send me.

Posted 10-Nov-17 1:27am

Member 12208944

Updated 10-Nov-17 2:16am

Add a Solution

3 solutions

Solution 1

Google will find you samples, or you can look at Multithreading with C++ and MFC[^]

Posted 10-Nov-17 1:37am

Richard MacCutchan

Solution 2

Have a look at Newcomer's Threads and Processes series.

Please note 50 ms is a relatively short time for Windows OS. Moreover, in order to keep your application responsive the 'active' (i.e. not sleeping) part of your code should be a small fraction of 50 ms (that is your thread should be sleeping most of the time).

Posted 10-Nov-17 1:48am

CPallini

Updated 10-Nov-17 1:49am

v2

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)

Jochen Arndt · Accepted Answer · 2017-11-10T02:16:00

Never use Sleep() in the main (GUI) thread.

As already mentioned there are multiple resources about threads.
An example is Using Worker Threads[^].

Based on that article you should create a worker thread and an event to stop the thread. Then the worker thread function can look like:

/*static*/ UINT CMyThreadClass::ThreadFunc(LPVOID p)
{
    CMyThreadClass * self = (CMyThreadClass *)p;
    bool bStop = false;
    while (!bStop)
    {
        switch (::WaitForSingleObject(self->m_StopEventHandle, 50))
        {
        case WAIT_OBJECT_0 :
            bStop = true;
            break;
        case WAIT_TIMEOUT :
            // Generate signal here
            break;
        }
    }
    return 0;
}

While this provides a better timing accuracy than a normal timer, it will still not be absolute accurate. If you use for example blocking socket calls in the worker thread, it might be necessary to adjust the time out value accordingly by measuring the execution time.