Callback Order Inconsistancy

[josefnpat]

So I was using the infamous gamestate library, and I stumbled across something odd;

The order that the callbacks are executed in don't seem to correlate with love's callbacks;

In love, the love.update is called before love.draw, whereas when gamestate has a foo:update and foo:draw, it calls foo:draw first, then foo:update.

This Inconsistancy threw me off, and if possible, it would be nice if reversed.

My current workaround is to use :init or :enter to set the variables before the library :draw's.

[vrld]

That's odd, because hump simply injects inself into the love callbacks, similar to this:

local _update = love.update
function love.update(dt)
    _update(dt)
    GS.update(dt)
end

Do you call GS.switch() inside love.update() or state:update()?

[josefnpat]

I do call love.update(), which means I am screwing up the state context; so in the end, this is my fault.

I thought gamestate would finish up the state as is, and it would switch the state once the whole love.run loop finished; so this would be user error.

Would that make sense as a feature request, to ask gamestate to finish up the current callbacks for the "cycle", and then switch after?

[vrld]

Should be fixed by 3c666c5