[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 101954] New: time wrong in applet clock (in different
From:       Paul Campbell <paul () taniwha ! com>
Date:       2005-03-20 3:22:35
Message-ID: 20050320042224.101954.paul () taniwha ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=101954         
           Summary: time wrong in applet clock (in different timezone)
           Product: kicker
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: kclockapplet
        AssignedTo: gebauer kde org
        ReportedBy: paul taniwha com


Version:           unknown (using KDE 3.4.0, Gentoo)
Compiler:          gcc version 3.3.5 (Gentoo Linux 3.3.5-r1, ssp-3.3.2-3, pie-8.7.7.1)
OS:                Linux (i686) release 2.6.10-gentoo-r6

starting with KDE 3.4 (really I think qt 3.3.4) the kicker applet clock's ability to show different \
timezones is broken. As I'm sure you're aware relative timezone offsets between timezones change over \
time. For example I live in New Zealand these days but work for a company near San Francisco, the time \
difference in NZ is a day a head and 3, 4, or 5 hours behind depending on whether NZ has DST, the US has \
DST or for a couple of small periods during the year (ie now) when neither does.

Anyway there are two bugs here - the first is very simple and has probably always been there - the clock \
code calculates the timezone difference when it starts up and doesn't assume that it ever changes while \
the applet is running ... in reality it probably should check about once an hour.

The second bug is the one that's bugging me at the moment - starting with QT 3.3.4 QT's changed the way \
it calculates QDateTime:secsTo() - which the clock applet uses to figure out relative timezone offsets, \
it doesn't for this any more and clocks in different timezones don't work correctly any more (at least \
for me here in the southern hemisphere), I'll attach a test program to this bug once it's submitted


[prev in list] [next in list] [prev in thread] [next in thread]