Function timing

[citrot]

Hi!

I would like to execute timed functions. Only wow lua support i found until now: "OnUpdate" event. Is there something else what is not based on graphical engine?

Thank you,

[Phanx]

Unless you're getting 2 FPS, and even then for most purposes, it doesn't really matter that OnUpdate is tied to your framerate:

local t = 5 -- do something 5 seconds from now
local f = CreateFrame("Frame")
f:SetScript("OnUpdate", function(self, elapsed)
     t = t - elapsed
     if t <= 0 then
          -- do something
     end
end)

Your other option would be to use the animation system:

local f = CreateFrame("Frame")
local g = f:CreateAnimationGroup()
local a = g:CreateAnimation()
a:SetDuration(5) -- do something in 5 seconds
g:SetScript("OnFinished", function()
     -- do something
end)

All existing timer libraries use one of the above methods.

In WoD the game will provide an actual timer mechanism, but the primary benefit to using it will likely be in reducing the amount of code that needs to be written to implement a timer, rather than offering any tangible performance boost:

C_Timer.After(5, function()
     -- do something
end)

[p3lim]

C_Timer would most likely be better for performance too, but no benchmarks have been done yet.

[SDPhantom]

I would think C_Timer.After() would be easier on resources since you won't have to create any UI objects to use. The only problem is you'll need to manage setting it up again if you want something to keep calling every so many seconds if you don't want to use Blizzard's Lua-defined Ticker factories (C_Timer.NewTicker() and C_Timer.NewTimer()). Note the Ticker factories return a table hooked into a metatable to control the ability to cancel a timer with entries for remaining iteration counts, a cancel flag, and a dynamicly-created callback function that is passed to C_Timer each iteration. This creates significantly more overhead than using C_Timer.After() yourself.

[p3lim]

Originally Posted by SDPhantom I would think C_Timer.After() would be easier on resources since you won't have to create any UI objects to use. The only problem is you'll need to manage setting it up again if you want something to keep calling every so many seconds if you don't want to use Blizzard's Lua-defined Ticker factories (C_Timer.NewTicker() and C_Timer.NewTimer()). Note the Ticker factories return a table hooked into a metatable to control the ability to cancel a timer with entries for remaining iteration counts, a cancel flag, and a dynamicly-created callback function that is passed to C_Timer each iteration. This creates significantly more overhead than using C_Timer.After() yourself.

Basically, unless you need to cancel it or need something that keeps repeating, use C_Timer.After.

[citrot]

Thank you for tipps. I think, i keep OnUpdate.