Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day, 11 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 12 hrs ago -
Maemo repository (3)
to Community by torsen - 2 days, 4 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 3 days, 1 hr ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 4 days, 8 hrs ago - more...
Tintin |
2009-10-28
, 14:21
|
|
Posts: 418 |
Thanked: 174 times |
Joined on Oct 2009
|
#131
|
Originally Posted by gman1
My time-line shown my current time. I'm using 0.92.7 - not sure if that makes a difference.
 |
|
2009-10-28
, 14:22
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#132
|
seems to work ok here, could it be a timezone issue?
__________________
Be warned, posts are often line of thoughts at highway speeds...
Be warned, posts are often line of thoughts at highway speeds...
|
|
2009-10-28
, 19:29
|
|
Posts: 24 |
Thanked: 0 times |
Joined on May 2009
|
#133
|
Originally Posted by tso
I don't know why, I haven't changed timezone settings or anything. The problem suddenly started happening today after months of working fine. I'll see if I can upgrade to .7 when I get to where there is wifi and see if that sorts it out.
seems to work ok here, could it be a timezone issue?
Edit: Upgrading to .7 didn't solve it. Powering down the n810 and rebooting did :P. Now to find out what changed in .7
Last edited by gman1; 2009-10-29 at 13:09.
 |
|
2009-10-31
, 10:52
|
|
Posts: 1,648 |
Thanked: 2,122 times |
Joined on Mar 2007
@ UNKLE's Never Never Land
|
#134
|
Can it be something with daylight saving time?
Last weekend in some parts of the world the clocks went 1 hour backwards.
Last weekend in some parts of the world the clocks went 1 hour backwards.
|
|
2009-10-31
, 23:58
|
|
Posts: 46 |
Thanked: 99 times |
Joined on May 2009
@ Sydney, Australia
|
#135
|
Originally Posted by gman1
I can't imagine anything that could cause the problem you described that could be cured by a reboot
Edit: Upgrading to .7 didn't solve it. Powering down the n810 and rebooting did :P. Now to find out what changed in .7
Even leaving that aside it is difficult to see what could have caused it. Did your daylight savings time end on the prior Sunday? Is your local shift to and from daylight savings a 1 hour shift?
| The Following User Says Thank You to trollo For This Useful Post: | ||
|
|
2009-11-11
, 14:16
|
|
Posts: 24 |
Thanked: 0 times |
Joined on May 2009
|
#136
|
Originally Posted by trollo
You're right. It didn't solve it. I'm stuck again. My location is set to Dallas, TX to get CST and my clock is set to the right time. My events in the edit window show the right time. On the calendar display they show an hour earlier than in the edit screen and my alarms go off an hour earlier than needed. All this did happen around the time we changed off of Daylight savings time in the US.
I can't imagine anything that could cause the problem you described that could be cured by a reboot
Even leaving that aside it is difficult to see what could have caused it. Did your daylight savings time end on the prior Sunday? Is your local shift to and from daylight savings a 1 hour shift?
Maybe this will help: Recurring entries I made long ago seem to be at the right times - edit window and calendar display match. Any entries I do now immediately end up with the one hour shift.
Last edited by gman1; 2009-11-11 at 14:59. Reason: addl info
|
|
2009-11-11
, 23:53
|
|
Posts: 46 |
Thanked: 99 times |
Joined on May 2009
@ Sydney, Australia
|
#137
|
Originally Posted by gman1
I have duplicated your problem by setting my location to Dallas - will try to get to this tonight but no guarantees as my time is at a premium until the weekend.
You're right. It didn't solve it. I'm stuck again. My location is set to Dallas, TX to get CST and my clock is set to the right time.
The behaviour is quite bizarre with more strange things happening than what you describe.
| The Following 2 Users Say Thank You to trollo For This Useful Post: | ||
|
|
2009-11-12
, 03:46
|
|
Posts: 4,783 |
Thanked: 1,253 times |
Joined on Aug 2007
@ norway
|
#138
|
location/time zone changes have always been troublesome for calendars, no?
|
|
2009-11-13
, 22:21
|
|
Posts: 46 |
Thanked: 99 times |
Joined on May 2009
@ Sydney, Australia
|
#139
|
Originally Posted by tso
The daylight savings time change shouldn't be a problem - I designed Seqretary to handle time zones well, which is why I implemented time zone handling from scratch - the standard time zone libraries could not do what I needed. There are time zone handling facilities there to handle future features like setting event times based on a different time zone to the one you are in and recurring event based on different time zones, as well as 2 different ideas of "local" time (for travelling).
location/time zone changes have always been troublesome for calendars, no?
I don't know what goes wrong with Dallas, but it worked flawlessly for Sydney. However having duplicated the problem it shouldn't take too much time to figure that out.
| The Following 2 Users Say Thank You to trollo For This Useful Post: | ||
|
|
2009-11-14
, 01:51
|
|
Posts: 46 |
Thanked: 99 times |
Joined on May 2009
@ Sydney, Australia
|
#140
|
Originally Posted by trollo
Dallas uses central time, which in the time zone information files for the US is based on Chicago. In 1936, Chicago switched from CST to EST on 1 March 1936. So the time zone information file shows 2 time zone offsets for "standard time" - being 6 hours (CST) and 5 hours (EST).
I don't know what goes wrong with Dallas, but it worked flawlessly for Sydney. However having duplicated the problem it shouldn't take too much time to figure that out.
In some circumstances the wrong one is chosen.
| The Following 2 Users Say Thank You to trollo For This Useful Post: | ||