Well, while this is a way to fix the issue, the problem - according to the tests I did some weeks ago - is not caused by math errors, but to the fact that for some reasons the SVGs we use aren't properly resized (it seems to be caused by the glow used there), so I'm not sure what's the best approach here.
In fact, using the old .png again fixes the issue, but it doesn't give us the visual quality benefits when scaling up the UI (same as the fix proposed here)... So maybe a compromise would be to just get rid of the smallest .svg icon (resources/launcher_icon_glow_62.svg), and going back with the png. Without logic changes.
Well, while this is a way to fix the issue, the problem - according to the tests I did some weeks ago - is not caused by math errors, but to the fact that for some reasons the SVGs we use aren't properly resized (it seems to be caused by the glow used there), so I'm not sure what's the best approach here.
In fact, using the old .png again fixes the issue, but it doesn't give us the visual quality benefits when scaling up the UI (same as the fix proposed here)... So maybe a compromise would be to just get rid of the smallest .svg icon (resources/ launcher_ icon_glow_ 62.svg) , and going back with the png. Without logic changes.