Bug 51565 - All clocks are in the same timezone as the first clock
Summary: All clocks are in the same timezone as the first clock
Status: RESOLVED FIXED
Alias: None
Product: kworldclock
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Matthias Hoelzer-Kluepfel
URL:
Keywords:
: 52637 53309 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-12-06 11:13 UTC by Ilya Konstantinov
Modified: 2004-06-03 11:00 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Fix (2.12 KB, patch)
2003-02-03 20:16 UTC, Sebastian Voitzsch
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ilya Konstantinov 2002-12-06 11:13:44 UTC
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!)
Comment 1 Jaime Torres 2002-12-17 13:28:05 UTC
This still happens in the 3.1 rc5. 
Also, when the mouse moves from one city to another, the time is always the same. 
Comment 2 Simeon Walker 2003-01-07 16:45:38 UTC
I see this too.
I am using Gentoo Linux and KDE 3.1rc5 and now 3.1rc6.
Comment 3 Philippe Fremy 2003-01-08 23:03:23 UTC
I confirm too on gentoo linux. Please move the status of this bug to open. 
Comment 4 Stephan Binner 2003-01-09 11:10:40 UTC
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. 
Comment 5 Stephan Binner 2003-01-23 11:50:18 UTC
*** Bug 53309 has been marked as a duplicate of this bug. ***
Comment 6 Stephan Binner 2003-01-28 19:55:34 UTC
*** Bug 52637 has been marked as a duplicate of this bug. ***
Comment 7 doug 2003-01-29 01:44:38 UTC
This bug still exists in the 3.1 release 
Comment 8 Sebastian Voitzsch 2003-02-03 20:16:18 UTC
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.
Comment 9 Stephan Binner 2003-02-04 16:12:36 UTC
Thanks for the patch, committed it. 
Comment 10 piechoc 2003-03-02 19:27:50 UTC
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(":"); 
Comment 11 piechoc 2003-03-02 20:21:18 UTC
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 
Comment 12 Sebastian Voitzsch 2003-03-02 20:42:24 UTC
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 
Comment 13 Sebastien 2004-02-03 00:36:44 UTC
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.
Comment 14 Sebastian Voitzsch 2004-02-20 23:21:03 UTC
Checked with KDE 3.2, kworldwatch works for me. Did you choose "save settings" after adding the clocks and/or flags?
Comment 15 Gabriel Ripoche 2004-06-03 10:58:43 UTC
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.