How to get timer id from onTimer() in WTL

[josip cagalj]

Hi, I'm working on some test app and i need help. I'm using vs2008 wtl. I add an handler for timer functionality and it looks like: MESSAGE_HANDLER(WM_TIMER, OnTimer), and implementationLRESULT OnTimer(UINT /*uMsg*/, WPARAM /*wParam*/, LPARAM /*lParam*/, BOOL& /*bHandled*/); Unlike old MSG_WM_TIMER(OnTimer)and implementation void OnTimer ( UINT uTimerID, TIMERPROC pTimerProc ) My question how can I get timer id out from param's in 'new' MESSAGE_HANDLER ontimer f.? Thanks in advance

[Stuart Dootson]

Look at the documentation[^] - wParam == timer ID. So, uncomment the relevant parameter's name in your implementation and use it. You should have something like this:LRESULT OnTimer(UINT /*uMsg*/, WPARAM _wParam_, LPARAM /*lParam*/, BOOL& /*bHandled*/);
or you could even alter the parameter's name to be more descriptive...LRESULT OnTimer(UINT /*uMsg*/, WPARAM _timerID_, LPARAM /*lParam*/, BOOL& /*bHandled*/);

[josip cagalj]

Thanks once again Stuart, indeed I've done so. UINT uTimerID = (UINT)wParam; Similarly I've get HDC out from WM_ERASEBKGND implementer; HDC hdc = (HDC)wParam; One question do, I'm getting error on my CRect member: "error C2065: 'CRect' : undeclared identifier" ??? Do I need additional include?

[josip cagalj]

By including 'atltypes.h'

[Stuart Dootson]

CRect is defined in atltypes.h in ATL in Visual Studio 2003, 2005 and 2008, or alternatively in atlmisc.h in WTL - if you're using one of those Visual Studio versions, I'd #include atltypes.h rather than atlmisc.h.

[josip cagalj]

THANKS! I've included atltypes.h now complaining about "error C2079: 'sTime' uses undefined class 'WTL::CString'" sTime - is my CString variable I have #define _WTL_USE_CSTRING in my stdafx.h

[josip cagalj]

Just remove my include 'atltypes.h' instead included 'atlmisc.h' no error now!

[Stuart Dootson]

See the "WTL CString support" section on this page[^] - you're probably better off using ATL's CString rather than WTL's, as ATL's CString is (now) MFC's CString, so may be more fully featured and optimised?

[josip cagalj]

Thanks, I've read the article and I must say it's a little ambiguous. Why couldn't I just leave it as is (including atlmisc.h) is it wrong? Everything is compiling ok?!

[Stuart Dootson]

You can - I'm just pointing out the options :-) I suspect that the WTL CString is no longer developed (I could be wrong), whereas the ATL/MFC CString is as mainstream as C++ gets in Microsoft development.