Thanks for the link I will have to look at it slowly.
It is basically a 3rd party graphics package that lets you manipulate images on the window. I am comparing the positions of 2 images and setting one of them in position in relation to the one being moved. The function returns a float for the image position and it has .123456 that many digits of precision after the decimal.
The movement of my code works fine, but it glitches and pops the 2nd image from time to time depending on the maths and comparison. Peter, you think if I cast the float to a double and then do the maths that it will be more precise and not glitch? I will have to try that.
PosX1 = 1234.123456000000032872776500880718231201171875
PosX2 = 2345.12345599999980549910105764865875244140625
With the output here I really did not expect that for PosX2. I thought it would be something like this.
2345.123456000000xxxxxxxxxxxxxxxxxxx //x is garbage numbers
To me that is 16 digits of precision and not the one below
To me that is only 9 digits of precision and the rest is off and then garbage. I don't understand? Are we saying that the display/string value is off but the actual binary representation is REALLY 16 digits of precision? More precise than what is being displayed?