Defect #277
javascript:setReplyTo() passes strings that turn into whole different ID's
0%
Description
When clicking on the msgid the inReplyTo field is filled with the ID. But somehow this gets mangled and you end up with a different number(!)
History
Updated by Patrick Talbot about 14 years ago
Actually tweet ids are internally BigInteger, which is a much bigger range than plain int.
I suppose that Servoy is parsing the number as an int, thus the conversion problem.
More like a Servoy issue than a plugin issue here...
I guess that I could accept a String and do the conversion to BigInteger in the plugin?
Updated by Robert Ivens about 14 years ago
I rewrote the solution to keep the tweet array as a formvar and STILL it mangles the ID's. It seems indeed that the problem lies in how Servoy handles this value.
62627492799852540 becomes 62627492799852544
But 62626627393290240 stays 62626627393290240. Others are different again.
So yes...better make it a string instead.
Updated by Patrick Talbot about 14 years ago
Yes, I guess there is a conversion problem (even when sending the value as a String in the setReply() javascript call) and I also suppose it's deep in Rhino's handling of JavaScript's numbers (as Integer or Double)
The only probable solution to this is to handle tweet ids parameters send as String, then do the conversion myself...
Updated by Patrick Talbot about 14 years ago
- Status changed from New to In Progress
OK, 0.8.5 will accept ids as String (and Tweet.getId() and Message.getId() will also be String BTW, because the conversion error started here!)
Coming soon...
Updated by Patrick Talbot about 14 years ago
- Status changed from In Progress to Closed
Fixed in v0.8.5 + updated sample solution