P. Clay Sherrod Mar 11, 2009
>
> ----- Original Message -----
> From: "Bill J Gray" <pluto@...>
> To: <guide-user@yahoogroups.com>
> Sent: Monday, May 11, 2009 10:43 AM
> Subject: Re: [guide-user] Re: Daylight "Saving" Time issues?
>
>
>> Hi folks,
>>
>> Many thanks to all who responded, both on- and off-list.
>> This is definitely a common problem. I have absolutely no
>> idea why. The relevant chunk of code in Guide has been
>> unchanged for about two years. (However, I got one off-list
>> reply mentioning finding the problem with the 2 June 2008
>> version, but not the 12 Mar 2008 one. So maybe some
>> "irrelevant" chunk of code is causing the problem, though
>> it's hard to see how!)
>>
>> Just to clarify: the problem involves Guide getting the
>> right time from the system clock. So those of us in, say,
>> Pacific Standard (or Daylight) Time, running Guide showing
>> one of those time zones plus UT, would see the correct eight
>> (or seven) hour difference between them. Guide is doing the
>> right conversion between time zones, and does so no matter
>> what time you set. It's just not getting the right "current"
>> time from the computer.
>>
>> The function Guide uses to get the system time, _ftime(),
>> seems simple enough: it returns (among other things) the
>> number of seconds elapsed since 1970 January 1 0:00 UT.
>> It looks as if it doesn't actually do that when DST is in
>> effect. I'm still investigating.
>>
>> In the meantime... best I can suggest is to hit Alt-J,
>> then enter TOFFSET=-1. With any luck, I'll be posting a
>> solution shortly. (After which you'll have to hit Alt-J
>> again and enter TOFFSET= , so that the clock isn't offset
>> by one hour anymore.)
>>
>> -- Bill
>>
>>
>> ------------------------------------
>>
>> To unsubscribe from this group, send an empty email to:
>> guide-user-unsubscribe@egroups.comYahoo! Groups Links
>>
>>
>>