Closed shaohu closed 7 years ago
Hi,
thanks for pointing us to the issue. We will try to take look but I am not sure when we get to it.
I believe it relates how the code retrieves the mantissa and exponent (see function getEXIFloat(value) on lin 1262 in https://github.com/EXIficient/exificient.js/blob/master/exificient.js)
If you have a fix/proposal let us know...
Thanks!
I also have a problem with numbers from the online demo. Here is my source file:
I'd say this is pretty important. The line number may have changed from 1262. Can you update? I wrote a test case for getEXIFloat(value) which I will report next.
Here is a test case you can try for getEXIFloat which shows (in my case, and I tested 4 numbers from the original problem report) that it's not the problem. Is the website up to date? getfloat.txt
Here's a very simple test case to show how horrible this bug is:
[-74.01046109936333]
Encodes and decodes to:
[-0.00001415142092]
Way way off!
Definitely the web site is out of date. I was able to download code here and make it work. Please update?
Your are right. The website was not in sync. You should not see the same issue after commit https://github.com/EXIficient/exificient.github.io/commit/4d51babb880d4acb9ca90f4dbf21b18d1d10d1d8
@shaohu and @coderextreme can you confirm that the issue has been fixed. If so let me know or close the issue yourself. Thanks!
Hi guys,
Firstly thanks a lot for this library, it helps a lot for my work. Good job!
When I tested the EXIforJSON functions, I found that there are some bugs on converting numbers. Attached is the test sample. In your online demo, when you convert these JSON scripts into EXI and then convert them back, the numbers in "coordinates" will change.
I will be very grateful if you guys can fix this bug. Or you can tell me where is the bug, probably I can also help with it.
Regards, Hu Shao