I had the same problem, as well, I think it had something to do with
where I got the date object from for me (if I create 2 new date
objects on the front end it would work fine, but if I got one of them
from the database then I would have issues). I just ended up doing a
getTime() on both of my d
Any word on this? I just verified that Date.compareTo() does not work
properly on Firefox,
Safari and Chrome on a Mac, but does work in hosted mode. I used a
TreeSet.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"G
Hi all,
I'm experiencing the same issue using GWT 1.7. Browsers tested:
Firefox 3.5.3 (Mac OSX), Safari 4 (Mac OSX), Firefox 3.0 (Linux).
I haven't tested the java.util.Date.compareTo(Date) output directly, I
simply found that the result of Collections.sort(List,
Comparator) is not correct if th
On 25 août, 16:52, pipo wrote:
> it seems the method Date.compareTo(Date myDate) does not work with the
> compiled version on GWT client side code but work perfectly in Web
> Hosted mode.
That's because hosted mode uses the pure-Java Date while web mode
("compiled version") uses a JavaScript e
it seems the method Date.compareTo(Date myDate) does not work with the
compiled version on GWT client side code but work perfectly in Web
Hosted mode.
Is it normal or is it a bug?
Instead of compareTo() I compare two dates using getTime() method.
--~--~-~--~~~---~--~-
