diff options
author | Daniel <kingdread@gmx.de> | 2020-05-01 12:51:06 +0200 |
---|---|---|
committer | Daniel <kingdread@gmx.de> | 2020-05-01 12:51:06 +0200 |
commit | cb757209d438afe23b5bdbfa5f62d00b195ad367 (patch) | |
tree | 3795c8241933c360bb9be099ede2e0d6e0cb85ca /src/filters/values.rs | |
parent | 9d5b728ce507334ad3916e2628dab1e0d82f5882 (diff) | |
download | raidgrep-cb757209d438afe23b5bdbfa5f62d00b195ad367.tar.gz raidgrep-cb757209d438afe23b5bdbfa5f62d00b195ad367.tar.bz2 raidgrep-cb757209d438afe23b5bdbfa5f62d00b195ad367.zip |
fix timestamp handling
As it turns out, the "local timestamp" as advertised by arcdps is a bit
misleading, because the timestamp is still in UTC. The "local" refers to
the fact that it can lag behind the server timestamp a bit (but usually
they seem to be within +-1 of each other), not that the timestamp is in
the local timezone.
This makes date handling a bit harder for raidgrep, but thanks to
chrono, not by much. The idea is that we simply deal with Utc pretty
much everywhere, except at the user boundary. This means that
1. Input timestamps for -before and -after are converted to Utc right
after input
2. When outputting, we convert to a local timestamp first
This makes the output consistent with the filenames now (and the "wall
time" that the player saw).
Diffstat (limited to 'src/filters/values.rs')
0 files changed, 0 insertions, 0 deletions