LÖVE

Jasoco wrote:If you look at the love.run function link posted above you'll see exactly when each part is executed. You can make your own love.run if you need to. I did a few times. In my case I had moved the love.clear call to before love.update so I could still use drawing commands in love.update for debugging purposes since I could then draw useful information inside a loop and not have to run that loop again in love.draw later. (Since by default anything you draw in update gets erased before it even gets shown.)

I had also made dt a global variable so I could access it from anywhere (Since it's very useful) instead of having to pass it through every function. Someone had once said it was a pretty good idea. But it'll remain local by default. But you can make it global if you have to.

love.run does change occasionally though. When we went from 0.7 to 0.8 it changed the way sleep worked and I had thought my games were broken.

function love.run()
...  
dt=0  --remove the "local" keyword?
...
end

bartbes wrote:Alternatively, one could just call love.timer.getDelta().

dwdcth wrote: Thank you ,your explanation is very helpful!
You said that you had made dt a global variabl.Do you do like this?

Code: Select all

function love.run()
...  
dt=0  --remove the "local" keyword?
...
end

bartbes wrote:Alternatively, one could just call love.timer.getDelta().

Jasoco wrote:One could. But I prefer to just make it global anyway. But only if I'm bothering to use a custom love.run(). Unless there's a drawback to having dt be global at all times vs. just calling getDelta() when you need it.

-- main.lua
local dt

function love.load()
  -- some code
end

function love.update(delta_time)
  dt = delta_time
  -- some code, using now dt, as usual
end

function love.draw()
  -- can access dt here, as upvalue
end

-- etc, same logic with others callbacks

dwdcth wrote:Yeah,it's a simple waw to make dt a global value.