tweens table makes Tween act like a singleton. about tween.lua

[kikito]

Hi dannifritz/technocat!

This is completely intentional. Being able to do tween.update(dt) only in one place, and having all the tweens updated, independently of the file they were created in, is good IMHO.

This relates with how Lua's require function works. The first time you invoke it, it reads the file you told it to read, and returns whatever it's supposed to return (a table, a function, nil, etc). Any subsequent call to require, however, will not parse the file; it has the result "cached", so it is returned directly instead of parsing the file again. So, in a way, require is designed to created "sort of self-contained singletons". So I try to use my libs in the same way.

Besides, I think in LÖVE in particular is very convenient; you just call tween.update(dt) inside love.update and everything works.

If you wanted to have several separated tween update cycles you have to use Lua's loadfile or LÖVE's love.filesystem.load . Both will create new closures every time their "returning chunks" is executed. In theory this will create several independent lists of tweens. But, I must warn you: I haven't designed the library with that in mind, and have not tested that behaviour. I'm pretty sure that will work. I'm not sure I'd want to use it that way though.

Best regards!

[dannyfritz]

Thanks for the reply. Glad it was intentional.
And thanks for the loadfile tip!