Displays one or more clocks which you can set to different timezones.
Features: - Each clock can have a defined GMT hour and minute offset - 24 hour or 12 hour formatting - Display or don't display seconds - Shows date per clock (can be hidden) - You can set a DST/Summer time per clock - Option to display leading zero for hours as well - Automatic new version checking! - You can access the config page by doubleclicking on any clock - You can change how many clocks you want "per row" and the widget height - A nice tabbed config view! - Alerts! Choose the clock you want, set the time and a message and the widget will start playing a sound at that time! - Choose clock GMT offset from a location list
New in 1.7: - Analog clocks!
Tip: want more precise control over where the clocks are? Run multiple copies of the widget. This way you can position them anywhere you want.
Note: if the config page doesn't open or the tabs don't work when clicking, try doubleclicking. There seems to be some kind of a performance issue with the analog rendering, but it doesn't seem to affect anything else.
Regarding time zones: is there a way to add the option 'last Sunday'? I am using 5th sunday of the month to make sure, but I am not sure what this does if there are only four Sundays in the month... We'll find out this weekend!
I'm having the same problems as mhowie. This is pretty bad. This widget could be so powerful, but with the wrong AM/PM indicator, the date changing at the wrong hour or rolling backwards...and now you're too busy? I'm sorry if I come across as a jerk, but this is essentially an untested alpha release, and you should withdraw it until you can get it working correctly.
crashy: ah yes. That... no, not possible unless you change the sourcecode. Anyway, I could add a field which would contain the settings and you could copy the contents of that single field and paste them into a field the new version and the new one would configure itself from that. Let's see if I can add that in the next version update.
mhowie: Gonna look at the code which calculates the time... prolly need to change something there to fix that.
Since we have to reconfigure every time there's a new version out, what if we dicided to keep the version but want to get rid of the annoying update link?
That's probably because those widgets always use your local time, which is stored in the JavaScript Date-object. This widget takes the UTC(GMT+0) time and calculates the timezone you want from that.
Downloaded the latest version and the AM/PM issue is fixed. The time/date is correct as well, but I fear at 8PM the date will revert to yesterday's date once again...don't understand the problem as the other comparable Opera widgets (e.g., "Digital Clock Widget") do not exhibit this bug.
Settings have to be reconfigured every time. It's a limitation in the current implementation of widgets in Opera.
The update message shouldn't show up in the new version. If it keeps showing, see if you can access http://admins.fi/~eagleeye/clockversion.txt which is the address that it uses to check for version updates.
Everytime i install a newer version, i have to re-enter all my settings. What the heck? How do i import my settings to the newer version? Is it possible to disable the "update" message?
Quick update! Now you can have analog clocks as well!
mhowie: I noticed a similar effect. My date was one day ahead near midnight... I'm trying to find the problem but it's a bit obscure. I did one change to the 1.7 version which might fix it, though.
but GMT.
By DataRat, # Aug 15, 2007 6:24:47 PM
By smrny, # Mar 21, 2007 8:31:40 PM
Limit min-width of the clocks to 120px
Center the clock titles
Add the weekday ("Mon") before the date
Then I add the timezone to the title to have that available too.
A future version might also automatically set the daylight savings time based on the timezone selected.
By Sigbjorn, # Nov 29, 2006 7:13:14 AM
By Micky, # Nov 5, 2006 6:44:10 PM
I did have that one "fix" but it just made things worse.
If any of you know javascript, feel free to look at the widget code... Most of the time and date related code is in clock.js
By zomg, # Sep 25, 2006 0:55:58 AM
By balkaster, # Sep 23, 2006 6:26:34 AM
By zomg, # Aug 26, 2006 9:03:57 AM
By mhowie, # Aug 26, 2006 6:03:30 AM
By mhowie, # Aug 24, 2006 3:16:55 AM
mhowie: Gonna look at the code which calculates the time... prolly need to change something there to fix that.
By zomg, # Aug 20, 2006 5:10:39 AM
By mhowie, # Aug 20, 2006 2:33:23 AM
Thanks.
By crashy, # Aug 20, 2006 2:16:40 AM
By zomg, # Aug 20, 2006 2:01:19 AM
By mhowie, # Aug 19, 2006 10:31:50 PM
The update message shouldn't show up in the new version. If it keeps showing, see if you can access http://admins.fi/~eagleeye/clockversion.txt which is the address that it uses to check for version updates.
By zomg, # Aug 19, 2006 8:28:35 AM
By crashy, # Aug 19, 2006 7:49:52 AM
It would seem the widgets size is causing trouble and it can't be avoided (?) for now at least.
By zomg, # Aug 19, 2006 7:25:17 AM
Intrestingly enough I don't get that problem, not even if I change my windows timezone to your timezone. o_o
By zomg, # Aug 19, 2006 6:35:52 AM
By mhowie, # Aug 19, 2006 6:33:42 AM
mhowie: I noticed a similar effect. My date was one day ahead near midnight... I'm trying to find the problem but it's a bit obscure. I did one change to the 1.7 version which might fix it, though.
By zomg, # Aug 19, 2006 5:01:00 AM