Re: problem CreateTimerQueue() in InitInstance

From:

"Alexander Grigoriev" <alegr@earthlink.net>

Newsgroups:

microsoft.public.vc.mfc

Date:

Sun, 2 Nov 2008 07:18:50 -0800

Message-ID:

<#3OjS5PPJHA.5076@TK2MSFTNGP05.phx.gbl>

"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
news:g5grg4tprr417vh1pkjf3c1e1p9m3iovcl@4ax.com...

plus notes in newsgroups.
I am still puzzled about a safe way to include a timing mechanism in
one of DLL's CWinApp members, someone suggested to include a invisible
window but I would prefer to run a separate (lightweight) thread which
calls a static method and updates regularly a counter (every second),

****
But using an invisible window uses a ZERO-weight thread because it
piggybacks on the main
GUI thread, so there is no additional performance penalty. However, it
*can* be delayed
by long processing in the main GUI thread.

You can create the thread anywhere BUT in the InitInstance; when I first
hit this problem
(back in the Win3.51-Win4.0 transition, I think) I just set a boolean flag
at every entry
point saying whehter or not the thread had been created, and if not,
created it then.
****

You're still not supposed to create windows in DllMain/InitInstance.
Kernel32 functions only, and not even all of those.