That's bizarre..bwexler wrote:Mark, I may have found another bug.
When I dowload my data it defaults to March 2090. When I atempt to type in more appropriate date at the bottom of the overview page it does not accept what I type.
For example I delete the first 2 digits in the custom from field and type <1><0>the <1> goes in the month field and <0> goes in the day field.
In the daily view I get the same default. Yesterday I scrolled through 75 years to the correct month. that worked. today I highlighted the year (2090) and typed in 2014 and that worked better.
I am not sure my current machine will last me untill 2090.
In 0.9.6 I had the problem with missing days when I forgot to put the SD card back in my PRS1 960. I was trying to check for that error when I found the one above.
I am running Windows 7 Pro Service Pak 1 on Home brew AMD FX 6200 6 Core 3.8 Ghz 16 GB RAM SH 0.9.8-1 64 Bit Open GL.
On PRS1, the dates are taken from the timestamps inside the block headers of the .001/.002/.005 files.
These timestamps are stored in very standard format, which is seconds since UNIX epoch, which was January 1st, 1970, 00:00am UTC, and pretty they are much impossible to screw up.
The conversions are done by Qt QDateTime function calls.
If you are importing and getting the wrong date, it's very likely you have a completely corrupted .00x file screwing things up on your devices SDcard. (The header bytes, which include the timestamps are protected by an additive checksum, and sessions that don't match this are dropped. There is a secondary 16bit checksum test, but it's switched off in the interests of import performance, as the likelyhood of this happening is very VERY low, i'll make sure to reenable this as a preference to make sure faulty sessions that pass the first checksum test get dropped.)
There is a slim possibility you have a corrupt value set to the clock drift in preferences...
If possible, I'd like to see a .zip (or .7z!) of your SDcard to try and replicate exactly what's going on here.
/Mark