Implicit conversion from float 802.696 to int loses precision - Trongate v1

Implicit conversion from float 802.696 to int loses precision
2 years ago

#1

Hope this question can help others as well some day!
Reading my issue happens when a float is coerced into an int. I know typesetting is a popular method in the framework for safety reasons and wonder if thats causing this?
Without going through all the code to remove int, is there a simpler solution?

2 years ago

#2

Hi Fin,

Have you updated your engine folder as I fixed this warning at the end of May:

https://github.com/trongate/trongate-framework/commit/82c12d7ab739f0b832864dde9581121d7d50f3c6

line 73 should read like so:

2 years ago

#3

Greetings,
No the lines do not match up, my Version: 1.3.3049. in license. Desktop app however says v1.0.005.
Thank you for pointing this out. I held off on updating on the june update until the final launch but now the option is not showing up any longer.
found this on how to update Trongate
(https://trongate.io/help_bar_threads/display/MRj2LjQTTEzX)
but my app is not updating.

github is anther panel to me like cpanel or whm. I dont understand the vocabulary or know / care to use it but I will take today to get familiar so I can "make a pull request on a repository " or whatever of the updated framework

2 years ago

#4

Thought I fixed things but still implicit conversion started showing up again. Lines 453 and 463 in Image.php, I put $height and $width in round() functions and problem solved.