pavelmachek ([info]pavelmachek) wrote,
@ 2008-04-02 01:15:00
Previous Entry  Add to memories!  Tell a Friend!  Next Entry
Daylight saving time is stupid idea
...and handling of time zones in vCalendar does not help. When you add an appointment to calendar in nokia 6230 (and similar, probably everything vCalendar based), the phone converts meetings to GMT, and stores them.

Unfortunately, with begining of daylight saving time, you move from GMT+1 to GMT+2... but your appointments stay there, and are now one hour off.

"Correct" solution would be to always enter timezone when entering appointment.

Workaround would be not to change timezone when dst begins, but lie to telephone, and set the time instead. Unfortunately, that would wreak havoc with synchronization, such as mobical.

"Reasonable" solution would be to assume appointments to be in "local" time zone, whatever that is. Just do not store that in GMT... but that's not how vCalendar works.

Is there chance of getting this mess cleared?

And before I loose them, here are some measurements from headlight I modded. Originally, it had 3 white leds, with optics making pretty narrow beam. I added 100mA, 90degrees red and green led.

On "almost empty" NiMHs (3x AAA), directly connected for white & green, current was: 18mA for white, 15mA for green and 26mA for red.

On freshly charged 900mAh NiMHs, current was 65mA for white, 54mA for green, 95mA for red. 82mA when running white+green.

I added switch selecting direct connection, 20 ohm resistor, and unknown blue resistor. With 20 ohms and fresh batteries, values are 28mA for white, 24mA for green and 50mA for red. Difference in light output is pretty minimal, and this setting is what I use when "very low" setting is not enough -- like going trot/gallop. White+green in this mode is very nice.

Unknown blue resistor and empty batteries gives about 3mA white (assuming 3mA on green?) and 6mA on red. Red is pretty unusable in this setting, you'll see objects above ground and branches trying to hit you, but not the ground itself. Green in this mode is OTOH very usable, providing nice light all around you, with visibility of few meters, and you can walk horse on this setting... not bad for 3mA (~10mW). This is actually too much light for eyes to go into highest-gain mode.


(Post a new comment)


[info]robbat2
2008-04-01 11:44 pm UTC (link)
That's almost as fun as a google calender bug I ran into, trying to put some international flights in.

HKG to YVR: departs HKG 14h20 HKST May 20, arrives YVR 11h35 PDT May 20th.
Google only lets you put an entire calendar into GMT, not enter timezones per event and start/end times. I'll bet it's going to SMS me at the wrong times for the items too.

(Reply to this)


[info]russdill
2008-04-02 01:26 am UTC (link)
This problem isn't as simple as you think. The entry must be stored with the time zone for which the meeting is scheduled. For instance, I'm in Arizona, we don't change have DST. But if I have a telcon that is scheduled by anyone outside of Arizona, the reoccuring meeting time must change based on the timezone where the meeting is actually scheduled.

Massive fail if your timezone and the meeting timezone differ in the date they start or stop DST or if it's in the opposite hemisphere.

(Reply to this)(Thread)


[info]russdill
2008-04-02 01:27 am UTC (link)
(err, sorry, thats what you said)

(Reply to this)(Parent)

It's a phone bug!!!
(Anonymous)
2008-04-02 02:15 pm UTC (link)
To me it's just a nokia 6230 bug... GMT is GMT, doesn't matters if your are in GMT+1 or GMT+2.

If I am in 28 Dec (Winter time) in Spain (GMT+1) and I create an appointment for 20 of May (Summer time, GMT+2) at 14:00. What should the phone store in his database? 13:00GMT??? NOOOOOOOO. The phone should know that 20 May will be GMT+2 and store 12:00GMT. Then when reading that appointment from the database the phone should convert 12:00GMT to whatever local time the phone is configured at that moment to present the date to the user.

I have an open bug about his -> https://bugzilla.novell.com/show_bug.cgi?id=352130

(Reply to this)


Create an Account
Forgot your login?
Login w/ OpenID
English • Español • Deutsch • Русский…