It just seems to get rounding right all the time, by pure chance.

I speculate it is because 255 is at the boundary of 2^8, meaning 255 in binary = 11111111. Maybe because all bits are on the floating point math has the desired rounding up.

grump wrote: Can you show an example where that happens? I had that only happen with r * (1 / 255), not with r / 255 No. I don't know how multiply is different than division for setColor() parameters but dividing does work. And it looks nicer. ;) Thanks for the correction. local CDIV = love._versio...

This thread could be moved to General but the point is for libraries which are made to work with ALL VERSIONS and to be ACCURATE. I see libraries using r/255, g/255, b/255 but that produces colors on the screen which can be off by 1 for each color component. Not a big problem but this can be avoided.

When making a library compatible with all versions concerning the new setColor parameters range such that lg.setColor(r, g, b, a or 255) becomes lg.setColor(r * CDIV, g * CDIV, b * CDIV, (a or 255) * CDIV) using the following formula is not exactly accurate. local CDIV = love._version_major >= 11 an...

I worked on updating Gooi with the color range changes in Love 11. The colors are better but not 100%. Get here:

https://drive.google.com/open?id=1FpOmO ... o7X4taF4km