Android Long Integer lossy (native function parameter) casting conversion about titanium-sdk HOT 8 OPEN

Not have any solution here but I've set a breakpoint in the send method and I can see that the parameter that is passed to that method is already a double:

from titanium-sdk.

Not have any solution here but I've set a breakpoint in the send method and I can see that the parameter that is passed to that method is already a double:

Thanks for your great support, maybe the problem occurs even then when the object attribute is set? Can you confirm that you initially see the number correctly, and that it is not the debugger doing the conversion incorrectly?

from titanium-sdk.

yes, I'm setting 12345678901 as a value (or Date.now()).

from titanium-sdk.

yes, I'm setting 12345678901 as a value (or Date.now()).

It seems to be Date.now() being cast to Double instead of Long then (Inside Java I suppose). But is working correctly when returned by Date.now() as toString() is doing right.

from titanium-sdk.

correct. But it's all long numbers. With to String it will be a string so it doesn't need to convert it. But I don't know at which point the conversion is

from titanium-sdk.

correct. But it's all long numbers. With to String it will be a string so it doesn't need to convert it. But I don't know at which point the conversion is

No, the Debugger is doing wrong!! :-/
It's not only send, but also the alert function called with Date.now() to rise the error!
I suppose that: If the toString conversion is done at JS level is ok, while if done at Java level is wrong!

from titanium-sdk.

I suppose that: If the toString conversion is done at JS level is ok, while if done at Java level is wrong!

I don't think it is doing a toString in Java as it still shows it as a number (double as you can see in the debug screenshot). But still: not a long as it should be.

from titanium-sdk.

I knew that JS try to fit all the datatypes in one putting pointers and other into the NaN space, but the long should not fit into a double NaN space. So I do not know what's happening...

from titanium-sdk.