| Welcome to Thunder Services! You are currently viewing our forum as a guest, which means you are limited to certain areas of the board and there are some features you cannot use. If you join our community, you will be able to access member-only sections, and use many member-only features such as the Thunder Arcade. Registration is simple, fast, and completely free. If you're already a member please sign in to your account. Register Now! |
Board Statistics
Total Forum Posts: 10,489
Total Members: 1,783 (The newest member is Batman)
February 15, 2011, 6:34 am, a record 85 users were online.
Total Members: 1,783 (The newest member is Batman)
February 15, 2011, 6:34 am, a record 85 users were online.
Active Users
5 users online in the past 15 minutes (0 Members · 5 Guests · 0 Anonymous)
Latest Posts
Apologies for prolonged waiting
Richard VII
Replies: 5
Replies: 5
Timestamp Glitch
Chris
Replies: 2
Replies: 2
Performance Improvement
Chris
Replies: 0
Replies: 0
Account Names now Locked In
Chris
Replies: 2
Replies: 2
Control Center Update
Chris
Replies: 4
Replies: 4
Polls
Apologies for prolonged waiting
Posted by ₪ Chris (Admin) at May 7, 2012, 11:59 pm. 5 comments
I will be finishing the Thunder Services application update very soon, my exams went well and the summer has begun for me. It will be just a few more days before I release the update
Timestamp Glitch
Posted by ₪ Chris (Admin) at March 29, 2012, 11:13 pm. 2 comments
You might notice a slight time glitch for the next hour. I just realized that my Time Module wasn't checking if Daylight Savings Time was active in London Europe ( the GMT timezone area ). With the way my system works, DST should never be factored into a stored timestamp, but it was being factored in because London Europe is currently observing DST and the timestamps I store are generated using this location for it's timezone. This problem has been corrected, and I believe all timestamps (after the next hour has passed) should be accurate and automatically synced with the time settings on your computer.
The glitch you may notice is that there are scores that were set in the "future" - but this is just a stamp that factored in DST when it shouldn't have, effectively putting the stamp one hour into the future.
The glitch you may notice is that there are scores that were set in the "future" - but this is just a stamp that factored in DST when it shouldn't have, effectively putting the stamp one hour into the future.
| ⌚ 3:17 PM May 18 |
