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.
Bug still present in latest version. As reported earlier, it has something to do with the GMT offset. As before, the selection of (-5 GMT), with or without daylight savings time being checked, results in the wrong date (one day previous) during the four hours between the offset and midnight.
If your general location isn't listed in the timezone box, let me know and I'll add it. Also, there might be some typos in the place names so let me know about them as well
Once again... 8PM and the date slips back one day. I suspect it corrects itself at midnight local time as the date in the widget is correct each morning when I check the computer.
Haven't had any luck reproducing that yet. I tried changing the windows time to your timezone and playing with the clock so the GMT time was 23:59 and seeing if the date would go wrong, but it didn't.
I did however, notice that if I moved the time back for enough to the date to go back, all the clocks would get stuck in one day behind the actual date until I switched back to the correct time... it seems it's something to do with the Date object in JS.
It just happened again...and I think it has something to do with GMT...I fired up Opera a little while ago, the widget opened as well, and the time and date were correct. At 8PM local, the date reverted back to yesterday. Not coincidentally (I don't believe), I am (-5) GMT, which is -4 with daylight savings applied.
So...the date reverted back at around (possibly exactly-- I wasn't watching) the time GMT was at 0000Z (new day)? Mmmm...
sommer: That's odd, unless you have a firewall you should be able to access that server. There aren't any blocks or such there as far as I know, although I've heard someone from China had some problems accessing a finnish IP address once... so if you're chinese...
I'll add more checks to the update-thing so it won't display the message if it can't access the page in the next update.
mhowie: Alright, keep me posted.
As for when the next update is coming, I'm currently working on some functions to Serialize my classes and Unserialize them so I can make the saving and loading better. It's currently getting a bit out of hand due to the increasing amount of data being saved and loaded... when I'm done with that, I'll add alerts and then it's update time
Strange...upon awaking this morning...a check of this widget (which, along with Opera, ran overnight) shows the correct date. I will continue to monitor and report.
Changing time zones does not remedy... and it is consistently one day behind. When I first installed (over the older build exhibiting the same problem), the date was correct--briefly...when I added my local clock and deleted the default (GMT) one, the problem arose once again.
That's odd... The way the date is calculated is handled internally by the JavaScript date object. In your case the code substracts 5 from the UTC time, so it should show the proper date as well.
Does it always show one day behind? Did you try changing the timezone for a test? I need something to help me find if there's anything wrong with the code, as when I try with -5 here, everything works just fine and so does every other timezone.
Weird...I am getting the wrong date with this widget. I noticed it with the last build and it has carried over to this one as well. My system time/date is correct and the widget time is correct. I am in the (-5 GMT) time zone and observe DST. The date being reported is yesterday's...
Everytime I exit opera and start it again this Widget doesnt automatically start. Is this a problem with this widget or does this happen with every widget? I wish it would automatically start with every startup of Opera because it's quite irritating to start the widget every time.
Update with the option to change how many clocks you want per row and the widget height if you happen to add so many clocks that they don't display properly anymore.
The config view is also tabbed now... the tabs are generated by a TabControl class I made. A bit WIP, because the colors etc. are hardcoded, but it works nicely otherwise
The next set of features is in the works... Working on selecting how many clocks you want "per row" and some alarm clock functionality as well. Stay tuned =)
My messagebox is just a div which gets added to the document (document.appendChild) and then it's removed (document.removeChild) after the user clicks OK and it's only shown when you start Opera/Widget.
I actually have a small object for drawing generic messageboxes which work a bit like alert() does in normal pages. It's not very good yet, but I'm working on it
On my widget, Type Master, for the messagebox to alert you when the game is over, I used a 'div' tag and when it's not being show I offset it off the screen. Maybe you could use the same technique for your alarm.
mhowie: it's currently a limitation in the way widgets store data. If they could access the disk to write a file, the changes could persist over versions but for now you'll have to reconfigure on update.
sommer: That's weird. It shouldn't happen. You seem to be the only one with the problem as well because nobody else has posted anything... can you tell me your OS and Opera version? Also, if the widget is unable to access the file on the server which contains the version data, it might say that there's a new version around. Make sure it can access http://admins.fi/~eagleeye/clockversion.txt (Configure firewalls etc.)
Thanks...
発言者 mhowie, # 2006/08/19 2:34:06
If your general location isn't listed in the timezone box, let me know and I'll add it. Also, there might be some typos in the place names so let me know about them as well
mhowie: I'll keep an eye near midnight for that.
発言者 zomg, # 2006/08/17 18:43:32
発言者 mhowie, # 2006/08/16 3:05:05
I've finished coding the new method for loading and saving data and have moved on to actual features now.
Fixed some bugs in creating a new clock, mainly related to the new clock getting wrong settings
Added a list of locations to the timezone selector, so you can now pick your location from the list instead of typing the numbers.
Alert configuration tab is done, I just need to write the actual alert code.
発言者 zomg, # 2006/08/15 8:53:44
I did however, notice that if I moved the time back for enough to the date to go back, all the clocks would get stuck in one day behind the actual date until I switched back to the correct time... it seems it's something to do with the Date object in JS.
発言者 zomg, # 2006/08/15 2:46:34
So...the date reverted back at around (possibly exactly-- I wasn't watching) the time GMT was at 0000Z (new day)? Mmmm...
Hope this helps you track down the bug.
発言者 mhowie, # 2006/08/15 2:03:52
http://172.20.125.81:9014/ ...
and I assume port 9014 is not open.
I will check at home if it works.
P.S.: Nope, I am not in China :-)
発言者 sommer, # 2006/08/14 18:08:06
I'll add more checks to the update-thing so it won't display the message if it can't access the page in the next update.
mhowie: Alright, keep me posted.
As for when the next update is coming, I'm currently working on some functions to Serialize my classes and Unserialize them so I can make the saving and loading better. It's currently getting a bit out of hand due to the increasing amount of data being saved and loaded... when I'm done with that, I'll add alerts and then it's update time
発言者 zomg, # 2006/08/14 13:00:13
発言者 mhowie, # 2006/08/14 12:35:05
But now I know why: I can't access clockversion.txt.
発言者 sommer, # 2006/08/14 9:44:07
発言者 mhowie, # 2006/08/14 5:38:42
Does it always show one day behind? Did you try changing the timezone for a test? I need something to help me find if there's anything wrong with the code, as when I try with -5 here, everything works just fine and so does every other timezone.
発言者 zomg, # 2006/08/14 5:19:52
発言者 mhowie, # 2006/08/14 4:50:45
You could try reinstalling Opera, which was suggested over at operas IRC channel.
発言者 zomg, # 2006/08/14 1:28:39
発言者 IchigoNL, # 2006/08/14 1:20:20
The config view is also tabbed now... the tabs are generated by a TabControl class I made. A bit WIP, because the colors etc. are hardcoded, but it works nicely otherwise
発言者 zomg, # 2006/08/14 0:49:15
発言者 zomg, # 2006/08/12 5:07:37
I actually have a small object for drawing generic messageboxes which work a bit like alert() does in normal pages. It's not very good yet, but I'm working on it
発言者 zomg, # 2006/08/07 21:27:50
発言者 sabrown100, # 2006/08/07 20:11:10
sommer: That's weird. It shouldn't happen. You seem to be the only one with the problem as well because nobody else has posted anything... can you tell me your OS and Opera version? Also, if the widget is unable to access the file on the server which contains the version data, it might say that there's a new version around. Make sure it can access http://admins.fi/~eagleeye/clockversion.txt (Configure firewalls etc.)
発言者 zomg, # 2006/08/07 19:39:39