Are MFC Timer(s) bad for performance in large projects (Vc++)
ATL / WTL / STL
1
Posts
1
Posters
1
Views
1
Watching
-
Hey out there, i'm heared that the use of timers in large projects is bad for performace. So is this true? I'm wondering, because i have done a new control using VC++/MFC and i use one timer in there. The timer only is created and the first time it's called i terminate it. Now someone said to me that i sould use ::GetTickCount() instead and save the first value and compare it again and again. It look more performance hungry than my timer solution. So what's your oppinion? Please don't answer something like i should do a test, i haven't so much time to test such things. And please answer only real facts and not only stuff like "i like timers more because i like it more" or "i like the TickCount solution more". Hope for a good discussion :)