C / C++ / MFC

Cyber Friend wrote:

At most how many timers can I use in an application as in future I will update my application for 32 threads?

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb

Jun Du wrote:

Whenever that program is run, it used up all 100% CPU. Of ocourse, the 20 timers have been later combined to one centralized, high-resolution timer.

anilksingh wrote:

I tried Sleep...

"The largest fire starts but with the smallest spark." - David Crow

"Judge not by the eye but by the heart." - Native American Proverb

// Code inside the thread function and m_number is the 
//variable for the edit box whose number property is set to true
CMyDlg *test=(CMyDlg *)pVoid;
	for(int i=0;i<1000;i++)
	{
		Sleep(10);
		if(flag==true)
		{
			CString s;
			s.Format ("%d",i);
			AfxMessageBox("Thread stoping on "+ s);
			return 0;
		}
		else
		{
			CString s;
			s.Format ("%d",i);
			test->m_number.SetWindowText (s);
		}
	}
	return 0;

Zac Howland wrote:

Alternatively, you could create a boolean flag and put a critical section around every access. This works just as well, but is error prone (one access without a critical section breaks the entire system). The Event solution doesn't have that problem.

VuNic wrote:

As said by David, never get your Sleep inside your thread or any loop, it puts the entire application to sleep