TimerUtils - Problems.

Hey guys.

I want to reuse as much of variables that I can now, and I started using TimerUtils.

However, I always get the error that there are no free timers, when I create the first timer. The start amount is 50.

Ignore my system double free, the timer problem is still there.

Thanks for helping.
CM_UP_v.0.0.2.w3x

disclaimer: I haven't opened your test map.

Which flavour are you using?? if you use red, try blue (just for testing)
Are you using properly ReleaseTimer()?? post code of your code...

It doesn't work with any of the flavors.
And its easier to check the map, since I only create one timer once and never again.

I do not release timers, because there is only one timer I need. (yet).

I don't have WC3 here, that's the reason. Then right now timerutils in general is useless for you. With just create a timer in a global variable that's enough for your needs.

Yes, but sooner or later I want to learn how to use that stuff, and I want to give the possibility to create a timer per instance.

So it wouldn't be useless.

How to use TimerUtils:

Replace CreateTimer() with NewTimer()
Replace DestroyTimer() with ReleaseTimer()

I personally would use Blue flavour for what you need it for.

I don't even destroy timers and I only have one function that creates a timer, using NewTimer().

Please check the map.

Struct initialization occurs before library Initialization. Move your NewTimer calls into a library intialization instead of the struct.

What Ammorth said. Generally, however, for a static timer that you never destroy, you should just use CreateTimer() instead of NewTimer(), problem averted.

Hmm yeah thanks, that was my mistake.

And why isn't it initialized before? I mean it requires the other library, doesn't that mean its onInit parsed after the requirement? At least it should

TimerUtil's NewTimer() method requires the TimerUtil's library be initialized before it can be used. If you use it from a struct's initializer, which is run before _any_ library initializers....

Oh I see. Damn so there is no other way around.

Yes I know, but I really like the static onInit method. So they are kinda useless?

Why? Because you can't do something you weren't supposed to do anyway? Seriously, just use CreateTimer().