DBI wrong time

  • Thread starter Thread starter noobmove
  • Start date Start date
  • Views Views 10,872
  • Replies Replies 58
  • Saying "it's a real pity, a shame, it was a brilliant app, please dev allow the community to make it live on" is not entitlement, it's gratitude and aknowledgement of the dev's work so good it ended up baked into users' habits as the go-to reference tool. how is that "can't even properly appreciate it"?
  • Entitlement would be "dev: you lazy ass, get back to work, you OWE us to keep working on it".
Please don't wave the entitlement card unncessarily.
"what's the big deal?" followed by "it wasn't even a commercial endeavor in the first place?" and two paragraphs of you going off on me when told that a dev doesn't want to go out of their way to do extra free work

yeah "entitlement" is the term to use here... "don't be a jerk"? ;)
 
It seems DBI is using outdated DST Time Zone data.
Not everyone is affected.
Most would be those that have changed their DST or GMT offset after the 1980s.

i.e. If i set time zone to Kuala Lumpur, DBI will show time -0:30.
Malaysia use to be GMT +7:30 but changed to GMT +8 in 1982.
If i set time zone to Hong Kong or Taipei, which is also GMT +8, will show the correct GMT +8 time.

If I'm not mistaken, Europe Berlin/Warsaw/Vienna changed their DST offset in 1981?
 
Yes. Due to bug 0 used instead of current time when looking up timezone info.
Post automatically merged:

That was fixed in 671 build
 
  • Like
Reactions: OrGoN3
Where can I find the v671?
Can't link it here because it resides on a disallowed site. It's also a beta and only in Russian.
Post automatically merged:

Thanks! Guess I haven't encountered any of those files yet.
No problem. Obviously there may be more differences, and if so, I'm sure duckbill will fill us in.
 

Site & Scene News

Popular threads in this forum