Back to General and Gameplay Programming

how can i use the CreateTimerQueueTimer()?

Joaquim Jesus · 2016-05-19T07:15:30

heres how i use the CreateTimerQueueTimer(): class Timer { private: static unsigned int TimerCount; PHANDLE m_timerHandle=NULL; UINT_PTR timerid; UINT m_uResolution=0; unsigned int TimerID=0; unsigned int intInterval=0; static void CALLBACK TimerProc(void* InstancePointer, BOOLEAN TimerOrWaitFired) { Timer* obj=reinterpret_cast<Timer*>(InstancePointer); if(obj->timerprocedure!=nullptr) obj->timerprocedure(); } public: std::function<void()> timerprocedure=EmptyEvent; Timer(std::function<void()> tmrprocedure=EmptyEvent) { TimerCount++; TimerID=TimerCount-1; timerprocedure=tmrprocedure; } void Stop() { DeleteTimerQueueTimer(NULL, m_timerHandle, NULL); CloseHandle (m_timerHandle); } unsigned int GetInterval() { return intInterval; } void SetInterval(unsigned int uintInterval) { intInterval = uintInterval; } property <unsigned int> Interval{GetProperty(Timer::GetInterval),SetProperty(Timer::SetInterval)}; void Start() { if(m_timerHandle!=0) Stop(); if (CreateTimerQueueTimer(m_timerHandle,NULL,TimerProc,reinterpret_cast<PVOID>(this),0,(DWORD)intInterval ,WT_EXECUTEINTIMERTHREAD)==0) DebugText("error\t" + to_string(GetLastError())); } ~Timer() { if(m_timerHandle!=0) Stop(); } }; unsigned int Timer::TimerCount=0; for now, i only get a memory leak... so what i'm doing wrong?

General and Gameplay Programming Programming

Started by cambalinho May 17, 2016 11:35 AM

21 comments, last by cambalinho 7 years, 11 months ago

Wyrframe

2,489

May 18, 2016 11:28 PM


        ULONG flags;
        DWORD dwPeridic;
        if(blnPeriodic==true)
        {
            flags = WT_EXECUTEDEFAULT;
            dwPeridic=(DWORD)intInterval;
        }
        else
        {
            flags = WT_EXECUTEDEFAULT | WT_EXECUTEONLYONCE;
            dwPeridic=0;
        }

        WT_SET_MAX_THREADPOOL_THREADS(flags,500);

Why not use the macro that actually exists, the way the documentation describes? The error you were getting is because the first parameter to the macro must be an assignable expression (an lvalue). Why do you need up to 500 threads to service your timer callbacks in the first place?

I have no idea what your (1) is asking.

As for your (2)... SetTimer() and KillTimer() deliver timer events as WM_EVENT events, and require a window handle. CreateTimerQueueTimer lets you specify arbitrary callback functions and callback parameters instead. AFAIK this design decision has nothing to do with the periodicity or precision of the timers associated with them.

RIP GameDev.net: launched 2 unusably-broken forum engines in as many years, and now has ceased operating as a forum at all, happy to remain naught but an advertising platform with an attached social media presense, headed by a staff who by their own admission have no idea what their userbase wants or expects.Here's to the good times; shame they exist in the past.

jpetrie

13,220

May 19, 2016 01:01 AM

i must use the CreateTimerQueueTimerWT_SET_MAX_THREADPOOL_THREADS() or i will get errors on lValue, like i said before.

That's because the macro is intended to modify the flags value given as the first parameter. It's not a function, its a textual substitution of an expression that performs and |= on the flags value. Don't treat it like a function. Call it like Wyrframe does in the above post.