Opened 15 years ago

Closed 13 years ago

Last modified 11 years ago

#5264 closed bug (fixed)

Set for local time work not properly

Reported by: damoklas Owned by: axeld
Priority: normal Milestone: R1
Component: Preferences/Time & Date Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

It Time appelet function "Clock set to:" – "Local time" or "GMT" work not properly: on the contrary.

Attachments (1)

BeOSHaikudifftimeset.jpg (159.6 KB ) - added by damoklas 15 years ago.
BeOS vs Haiku

Download all attachments as: .zip

Change History (14)

comment:1 by damoklas, 15 years ago

In east of Greenwich Time must be added, not subtracted. To the west of Greenwich Time must be subtracted.

comment:2 by siarzhuk, 15 years ago

Have you seen this: #3903?

in reply to:  2 ; comment:3 by damoklas, 15 years ago

Replying to siarzhuk:

Have you seen this: #3903?

Have you seen how this work on BeOS? On BeOS this work different then on Haiku. On BeOS that work correct.

by damoklas, 15 years ago

Attachment: BeOSHaikudifftimeset.jpg added

BeOS vs Haiku

comment:4 by stippi, 15 years ago

Are both installations configured to be in the same time zone?

in reply to:  3 ; comment:5 by zooey, 15 years ago

Replying to damoklas:

Replying to siarzhuk:

Have you seen this: #3903?

Have you seen how this work on BeOS? On BeOS this work different then on Haiku. On BeOS that work correct.

Strange - at least when I check just now, it worked just the same as on BeOS: with these two buttons you tell the system what time your hardware clock is using. So when you switch from GMT to local time (let's say CET), the result will (and should) be that the clock will be set backwards by the difference (for CET it'll be one hour).

I have no idea how you managed to create the pictures for BeOS that you posted here.

comment:6 by damoklas, 15 years ago

Maybe that mean "BIOS clock set to:" not OS clock?

in reply to:  5 comment:7 by damoklas, 15 years ago

I have no idea how you managed to create the pictures for BeOS that you posted here.

I use +2 time zone, not +1 (they work different, ?)

comment:8 by damoklas, 15 years ago

I found that BeOS use false time zone for Vilnius. It set it to +1 instead of +2. Looks like ths observed issue was result of this shift. Haiku use +2 for Vilnius time zone that is ok.

  • May be we should "explain" the description "Clock set to:" to something like "Hardware clock set to:" or "BIOS Clock set to:". This make the things a bit cleaner for unfamiliar user - and let to avoid some misunderstanding. I meant replace the "Clock set to:" to more descriptive one "Hardware/BIOS clock set to:"
Last edited 11 years ago by mmadia (previous) (diff)

comment:9 by damoklas, 15 years ago

set bug to "strange" and finish. Maybe: "Hardware clock set to" is better idea.

comment:10 by siarzhuk, 15 years ago

Just to "bury" this ticket. We propose to change the following lable in the Time Preflet from "Clock set to: GMT/Local" to the one of:

a) "Hardware clock set to: GMT/Local"

b) "BIOS clock set to: GMT/Local"

c) "PC clock set to: GMT/Local"

d) More clear variant?

AFAIK, this option is a Haiku-only feature and should be more self-explaining for newbees. I personally know at least 3 peoples that have had incomprehension with this customization concept. And I suspect we will have the question "Which clock is set to GMT?" arising again and again. So I propose this self-explaining label for this. Are there any objections?

comment:11 by stippi, 15 years ago

I'm all for "Hardware clock set to: GMT/Local".

comment:12 by stippi, 15 years ago

Perhaps even with an explanation that Windows usually has it set to "Local".

comment:13 by leavengood, 13 years ago

Resolution: fixed
Status: newclosed

I have changed the label to what stippi suggested and added a fairly long tool tip which I hope explains things well enough in hrev41957.

Note: See TracTickets for help on using tickets.