Version: (using KDE Devel) Installed from: Compiled sources To reproduce: 1. Right-click the map and select Clocks -> Add. 2. Select timezone "America/Los_Angeles" and click OK. 3. Right-click the map and select Clocks -> Add. 4. Select timezone "Asia/Jerusalem" and click OK. 5. Notice both clocks are showing the same time, with the first clock being the correct one. (Those locations are separated by 10 timezones!)
This still happens in the 3.1 rc5. Also, when the mouse moves from one city to another, the time is always the same.
I see this too. I am using Gentoo Linux and KDE 3.1rc5 and now 3.1rc6.
I confirm too on gentoo linux. Please move the status of this bug to open.
Philippe: The bug status is open and according to bug history was never closed!? If you want to confirm the bug then do it with your pfremy@kde.org account.
*** Bug 53309 has been marked as a duplicate of this bug. ***
*** Bug 52637 has been marked as a duplicate of this bug. ***
This bug still exists in the 3.1 release
Created attachment 872 [details] Fix Seems the issues from #4833 are solved too. Patch addresses wrong labels and incorrect time display in both map display and panel clocks.
Thanks for the patch, committed it.
using the patch gives this error: zoneclock.cpp: In member function `void ZoneClock::editClock()': zoneclock.cpp:100: syntax error before `)' token The last parenthesis in line 100 should be removed: - _dlg->ClockZone->currentText().append(":")); + _dlg->ClockZone->currentText().append(":");
Sorry for the nonsense in my last comment, please forget it. Probably the line 54 in the patch should read _nameLabel->setText(_dlg->ClockZone->currentText().append(":")); and not _dlg->ClockZone->currentText().append(":")); Nevertheless the patch doesn't seem to work. It compiles with the warnings In file included from libww_la.all_cpp.cpp:3: mapwidget.cpp: In member function `QString MapWidget::cityTime(QString)': mapwidget.cpp:321: warning: unused variable `time_t t' In file included from libww_la.all_cpp.cpp:5: zoneclock.cpp: In member function `void ZoneClock::updateTime()': zoneclock.cpp:129: warning: unused variable `time_t t' and all the clocks now show 00:00:00, 28.02. 093
Seems as if you're trying to update an old version of kworldclock and/or did some changes to the patch. The patch was created using files from KDE 3.1RC6. The first "error" you reported (the parenthesis) appears in a line that is commented out (note the '//' at the beginning of the line), so the compiler will completely ignore this line and it's impossible to get an error message from this part of the patch. For some reason you removed the '//'.... Try a newer version of kworldclock or get the newest cvs as the patch is already commited. Sebastian
I've downloaded Mandrake 10.0 preview and it has KDE 3.2 (3.1.94). This bug STILL HERE ! Perhapse it has been corrected in the current beta2 or RC1 but I have no hope... Could you confirm you can create two clocks with two timezone, restart KDe (or kicker) and then have those two settings keeped ?? Thanks.
Checked with KDE 3.2, kworldwatch works for me. Did you choose "save settings" after adding the clocks and/or flags?
I still see this problem in KDE 3.2.0 (tested with "plain" and "digital") The problem appear only when the "date" field is not displayed. If I check the "date" field in each clock, everything work fine. But if I do not check the "date" field, then the clocks without date will display the "local timezone" (setting Tz=0 in config file, i.e. the default). Can someone reopen this bug? I found bug 43586 that looks like a dupe, and which is also marked resolved although someone still has the problem with 3.2.2.