... the user friendly GPS tool

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Bug in duration shown for my tracks
(13.07.2009, 18:22)routeconverter Wrote:
(13.07.2009, 16:42)RsH Wrote: GMT: Jul 13, 2009 11:15:39 AM
milliSeconds: 0 cal: Dec 31, 1969 7:00:00 PM
minus one hour: Dec 31, 1969 6:00:00 PM

That's the main line for me: it seems the locale has an effect on the time, i.e. 0 milliseconds is not Jan 1, 1970 00:00:00 in every Locale. I've read the Java code for a while now but still don't get the reason for this.

Anyway, please try the latest prelease 1.28.1 and send the output to this thread.

Just downloaded the latest prerelease in both exe and jar versions and both show 1.27.16 as the version... and the time is still at 18:00 with the command prompt window showing the same values as before. Let me know when 1.28.1 is available.

It's now 1AM here in Toronto and I just did the downloads again and it is still showing 1.27.16 as the version I downloaded, both for the jar and the exe.

RsH [aka Bob]

Messages In This Thread
Bug in duration shown for my tracks - by RsH - 02.07.2009, 16:38
RE: Bug in duration shown for my tracks - by RsH - 13.07.2009, 20:15

Forum Jump:

Users browsing this thread: 1 Guest(s)