C / C++ / MFC

acerunner316 wrote:

Isn't this similar to what I'm already doing, posting messages every 10ms?

Chris Losinger wrote:

pretty much. but Sleep simply isn't that accurate. Sleep uses the system clock, which has a resolution closer to 15ms per tick in most modern versions of Windows. and, it's entirely possible for your sleeping thread to get preempted by another thread, further delaying its awakening.

acerunner316 wrote:

I am using Sleep(10) in my thread to post a windows message every 10ms.

UINT CNOx1000MonitorDlg::FThreadLoop (LPVOID PptrToClass)<br />
{<br />
	CMainWindowDlg *LptrClass = static_cast<CMainWindowDlg *>(PptrToClass);<br />
	HWND *ptrWindowHandle = new HWND;<br />
	*ptrWindowHandle = LptrClass->GetSafeHwnd();<br />
<br />
	while(LptrClass->mbolThreadExecute)<br />
	{<br />
		::PostMessage(*ptrWindowHandle, WM_UPDATE_CONTROLS, 0, 0);<br />
		::Sleep(10);<br />
	}<br />
	delete ptrWindowHandle;<br />
	return 0;<br />
}

acerunner316 wrote:

but 6ms delay is still way too slow

ceejeeb wrote:

yes it is the width