C / C++ / MFC

#include <windows.h>
#include <iostream>

void CALLBACK myOnTimer(HWND hwnd, UINT uMsg, UINT_PTR idEvent, DWORD tickCount)
{
  std::cout << "Timer. id = " << idEvent << ", tick = " << tickCount << std::endl;
}

int main(int argc, char * argv[])
{
  MSG msg;

  UINT_PTR timerId = ::SetTimer(0, 42, 1000, myOnTimer);

  std::cout << "Timer set, id = " << timerId << std::endl;

  // This is done by MFC in your application but needed for the example.
  while(GetMessage(&msg, 0, 0, 0))
  {
    TranslateMessage(&msg);
    DispatchMessage(&msg);
  }
  return 0;
}

'SetTimer' : cannot convert parameter 4 from 'void (struct HWND__ *,unsigned int,unsigned long,unsigned long)' to 'void (__stdcall *)(struct HWND__ *,unsigned int,unsigned int,unsigned long)'

void __stdcall myOnTimer(HWND hwnd, unsigned int uMsg, unsigned int idEvent, DWORD tickCount)
{
  // ...
}

shanmugarajaa wrote:

how to create "TIMERPROC"..

#define IS_LEAP_YEAR(y) ((y) % 4 == 0 && ((y) % 100 != 0 || (y) % 400 == 0))

inline bool isLeapYear(int year) const
{
    return year % 4 == 0 && (year % 100 != 0 || year % 400 == 0);
}

A child window that is moved or repositioned in the Z order during the enumeration process will be properly enumerated. The function does not enumerate a child window that is destroyed before being enumerated or that is created during the enumeration process.

xrg_soft@163.com wrote:

Does anybody know in which case will the risks(caught in an infinite loop or referencing a handle to a window that has been destroyed) happen?