I just answered a similar question in another post... :o)
I would have only the main thread do the GUI handling and send a message to
the window with the control you want to up update (the dialog) from the
other thread with information about what you want it to do. In other words,
only the main thread should be doing the actual UI updates and the other
thread would just send it message that tell it to do those updates. Since
you're sending the messages from a worker thread you can safely use sleep()
to have it wait for a while rather than using a timer.
This is an interesting article on this subject:
http://www.kbcafe.com/articles/HowTo.Thread.pdf#search=%22C%2B%2B%20sleep%22
Tom
"PaulH" <paul.heil@gmail.com> wrote in message
news:1155935901.209932.100560@h48g2000cwc.googlegroups.com...
I have an MFC app that can be used with or without the dialog (GUI)
component. The dialog is an optional status component that updates with
statistics every second. I'd like to put all the statistical
calculations and queries in the App. The Dlg and the App run in two
separate threads.
My question is: what's the best OO method of doing this?
1. Do I put a timer in the dialog and have it get the data from the app
every second?
CMyDlg::OnTimer()
{
STATISTICS stats;
((CMyApp *)GetParent())->GetStatistics(&stats);
//...
}
2. Do I send a pointer to the statistics to the dialog from the App and
just have the dialog read that every second?
CMyApp::CreateDialog(CWnd *pParent)
{
m_pDialog = new CMyDlg();
m_pDialog->SetStatisticsPointer(&m_statPointer);
m_pDialog->Create(IDD_MY_DLG, pParent);
//...
}
Neither of these strikes me as a particularly fantastic solution... Is
there a better way?
Thanks,
PaulH