On Tue, Apr 6, 2010 at 5:38 AM, Dick Kriss <[email protected]> wrote: > Interesting there is no UTC offset for users to set in fldigi. How > does fldigi determine the correct offset based on local computer > time? Sounds really hard to program with no user preferences. > > I assumed (probably wrong?) that fldigi used the QTH or the > Locator in the Operator configuration panel to know how to display > the correct UTC. >
Unix systems, e.g. Linux and MacOS, maintain the internal system real-time clock at UTC/GMT. When you set the TZ environment variable that tells the date-time routines what offset to use when displaying and setting the time. This reflects the multi-user history of Unix, where simultaneous users could be in different time zones when using the machine. Conversely, Windows sets the system real-time clock to local time. Windows assumes (rightly so) that the user will be sitting in front of the machine so that machine only really operates in one time zone. You get to experience this problem when you dual-boot a windows/unix system and the system time is loaded from the battery-backed hardware clock. Apple's approach when running Bootcamp (dual boot) is to install a filter program in Windows that makes the correction so that the hardware clock continues to run in UTC. So, which approach should fldigi assume? I think that the approach Stelios describes is the one that makes sense. -- 73 de Brian, WB6RQN/J79BPL
_______________________________________________ fldigi-alpha mailing list [email protected] https://lists.berlios.de/mailman/listinfo/fldigi-alpha
