[hump.timer] Subject values are not precise to targets after timer has completed about hump HOT 6 CLOSED

You could use the after callback of the tween function.

https://hump.readthedocs.io/en/latest/timer.html#Timer.tween

Example:

local Timer = require "hump.timer"

local fade = {
    0
}

love.update = function(dt)
    Timer.update(dt)
end

love.draw = function()
    love.graphics.setColor(255,255,255,fade[1])
    love.graphics.rectangle("fill", 200, 200, 200, 200)
end

local fading = false

love.keypressed = function(key)
    if not fading and key == "space" then
        fading = true
        if fade[1] == 0 then
            Timer.tween(5, fade, {1}, "linear", function()
                fading = false
            end)
        else
            Timer.tween(5, fade, {0}, "linear", function()
                fading = false
            end)
        end
    end
end

from hump.

@usysrc This is a good workaround, but the precision issue still exists.

from hump.

there is no precision issue, the value is correct inside the after function

from hump.

There is, because of the way floating point values work. Otherwise, the example I showed in my initial post would always work, without the need for math.floor.

One way to solve this issue might be to set the subject to the target value after the timer is complete. While this would be a hacky way of fixing the issue, it would work.

Actually, now that I think about it, this could cause unexpected results in some cases (such as if the subject were changed at all during the timer), so never mind.

from hump.

These are floating point numbers. It is just the way it is. But if you need the target value you can get it inside the after function.

Timer.tween(5, fade, {1}, "linear", function() print(fade[1], fade[1] == 1) end)

from hump.

I see. I guess this can't be worked around, so I'll close this issue.

from hump.